Posted5 days 7 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) in How-To and Troubleshooting
Recent comments
- In Backdrop CMS the update.php file located in the /core folder (mydomain.com/core/update.php).
- For launch the update.php from address bar of the browser, without restrictions, you...
Thanks. I've now tested this on a localhost and what you say holds true: the user whose permission has been removed for the given content type no longer has creation and editing rights for that...
I finally found the PHP controle in my CPANEL and Reset the PHP to vwersion 7.3. Using this version I was able to clear the update caches but I am still unable to run update instite of the...
OK so looking a the results of running update.ph[ it calls for a specific version of PHP. My host company is providing a 8+ version of PHP. One now wonders if therre is a general limit on PHP...
I think, the user simply will not be allowed to create / edit / view node. This should not somehow affect to existing publications. Current rights and publication status have no connection.
Comments
Here are some issues I would like to talk about or revisit (as time permits) during the Weekly Dev meeting or during the Design/UX meeting.
Better defaults position for breadcrumbs on installation of new sites.
https://github.com/backdrop/backdrop-issues/issues/4113
Config Recipes
* What can we do for the next release?
* How do we promote this? Is this a few feature (in theory, except for a bug it was there before)?
https://github.com/backdrop/backdrop-issues/issues/3763
Add a 'User: compare' visibility rule
Is this a good feature for core? Can we get it working for this release?
https://github.com/backdrop/backdrop-issues/issues/4029
This batch of issues
Add a new pageless node above the "Promoted Content" block on Home page
https://github.com/backdrop/backdrop-issues/issues/4849
Provide a new 'hidden-path' content type OOTB, and use it as a content block
https://github.com/backdrop/backdrop-issues/issues/4903
[UX] Change default home page from 'user' to 'node' - if user removes path to home
https://github.com/backdrop/backdrop-issues/issues/3343
A recent update with our long-standing symlink problem: Issue 3008
There's now a simpler alternate approach with less impact. Some core dev eyes are welcome.
The purpose is, to solve the initial problem soon. If people need more elaborated solutions for special cases, this could be a follow-up.