I'm not able to reproduce this behavior. I only get this behavior if I visit node/add/page and then re-open node/add/page from the admin menu (effectively opening the page twice in a row). I think this is the expected behavior in this case, since the previous page was node/add/page
Posted4 days 22 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) in How-To and Troubleshooting
Recent comments
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
I'm not able to reproduce this behavior. I only get this behavior if I visit node/add/page and then re-open node/add/page from the admin menu (effectively opening the page twice in a row). I think this is the expected behavior in this case, since the previous page was node/add/page