search

modxcms / revolution

MODX Revolution - Content Management Framework
https://modx.com/
GNU General Public License v2.0
1.35k stars 527 forks source link

"New document" button context key based on user-permissions #10172

Open bertoost opened 10 years ago

bertoost commented 10 years ago

bertoost created Redmine issue ID 10172

When a user only has permissions for other contexts (not 'web') and then clicks on "new document" above the resource tree, then the &context_key=web parameter is added to the URL, this creates an "access denied" error

StevenMorgan commented 10 years ago

This sounds pretty important, fundamental usability issue with multiple contexts and the top nav above the Resource Tree.

Can we Priority tag?

rtripault commented 10 years ago

A solution would be to use the default_context setting

StevenMorgan commented 10 years ago

This won't solve where Users have access to multiple Contexts, but it will certainly be a step in the right direction.

Some type of "Active Context" setting would be great based around Active Resource in the Tree.

If this is challenging to achieve I suggest we patch with default_context and revisit at a later date.

wuuti commented 9 years ago

more general: shouldn't all the action icons from above the resource tree go down into the context sections? There is already a plus-icon for adding new documents at the context levels, so it's just adding the symlink, weblink and static as small icons there. And of course the purge/trash icon - if we move it into the context sections, it could purge only the deleted resources of that context - not of all contexts in the installation. Could be something like this:

context_proposal

By placing the icons in the context sections we can also honor different permissions per context for the other types of resources as well.

smg6511 commented 4 months ago

This is quite an oldie here! I think the ultimate solution is to mirror what 3.x has done—simply remove those action icons above the contexts. In 2.8.7, each context has a simple create action button (and refresh one), just as the current 3.x version does, and the contextual menu has access to all relevant actions otherwise.