can't make document tree visible to restricted user

Thanks everyone!! All comments very helpful. I think the first problem was, in fact, related to lingering cache issues. I removed the "resource_tree" permission and did a lot of fiddling and eventually got the elements tree to display by itself with all of the elements the restricted user is supposed to see. IOW, it's working right.

The "permission denied" problem is still occurring. So, to be clear, here is the list of context access permissions that are currently set:
change_password -- change_profile -- edit_chunk -- element_tree -- frames -- help -- home -- list -- load -- logout -- menu_site -- menu_support -- menu_user -- save_chunk -- view_chunk

The only elements the user can see are the two chunks he can edit. The other tabs are not visible. None of the other element types are visible, nor is element category2 which contains all of the chunks he's not allowed to see.

You can go in and make a change, click save and you get the "successful" message. Then before coming back to the normal dashboard display, the error window "permission denied" shows up. It has the feel that something is happening in the MODx logic after the chunk is successfully saved that requires a permission that is not active. Some view option that needs to be set? There is no error when the user first logs in, so it's hard to guess what would come after saving a chunk, before displaying the dashboard, that doesn't happen when you log in. Posting a log record? Trying to do something with the resource tree or file tree? You can see that the element tree as been rendered prior to the error message being thrown.

I flushed permissions and sessions, deleted the contents of the core/cache directory using my ftp client, and cleared my browser cache. I've also done a lot of fiddling with permissions that look "promising" (read: more likely than the other minuscule probability permissions).

Thanks again for pitching in with your help. I'm willing to keep working on this as long as someone is listening.

Rick.

@sottwell:

This is because it adds itself to the Manager's resource groups, hence changing yours (and everyother administrator's) permissions and altering the content of the Manager at the same time. Typically requiring a flush and cache. However, the top menu, often requires a logout/login too (which actually takes care of a lot of it).

Quote from: sottwell at Aug 28, 2012, 11:42 AM

Sometimes I have to flush permissions after installing a package with a Components menu action before it will show up in the main menu. Clearing the cache, even deleting the core/cache folders, won't do the trick.

I've found a number of cases where clearing the cache has no effect, but reloading the Manager page does.

As a side note, I've also discovered that reloading the Manager page solves the blank console problem in Chrome for me (and other occasional anomalies in the Manager). It's always required after searching locally for packages and often after installing a package. Strangely, the blank console is only an issue on my localhost Windows install, which means I could probably solve it by messing with the XAMPP configuration if I only knew what to change.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

@ride2719:

I wish I could help with this. I don't actually have any multiple users in any of my managers. So, I'm not sure what is necessary here.

I've never been able to pin down the "blank console" issue. It seems to happen at random on all Revo installations I've ever worked with. More often when clearing the cache than when managing packages, but it's definitely a puzzler.

Quote from: sottwell at Aug 29, 2012, 12:29 AM

I've never been able to pin down the "blank console" issue. It seems to happen at random on all Revo installations I've ever worked with. More often when clearing the cache than when managing packages, but it's definitely a puzzler.

In my experience, it almost always happens immediately after searching locally for packages, visiting the repository, or installing a package and it *never* happens if you reload the Manager page right before clearing the cache or installing a package.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html