I've meant to tackle this, but didn't till today when you posted. I'm not getting your error, and I can't see why it would continue to show access denied after displaying access, but I have seen that before (on admin mostly) after modifying policies. Refreshing the tree, or page usually brings everything back to normal. Beyond that, I'd clear the core/cache folder and check to make sure I'm using another browser to check the new media source editor user. I've managed to neglect to check which browser I'm using and log in as a user when I'm already logged in as admin in the same browser in the past.
I did hang up on closing access to the filesystem. And I think I've found something important. I have no media source access policies to choose from. I'm going to take this to another thread, because out of four 2.2.5 sites, none of them have the same media source templates, settings, or policies. All upgraded within the past week and a half, all running just fine otherwise.
-
- 1,024 Posts
Clearing the cache is off course something tht is done also as in the tutorial. I notice that as soon as I limite access to the filesystem for the administrator only. It seems that the exception for the editor user no longer works. However in the tutorial it all works.