My most important category has completely disappeared from manager

If you have any thoughts on how this could be improved (other than by better documenting the above points), I’d love to hear them.

I actually had two ideas run through my head while getting ready for work this morning:

• Make the visibility of element categories and resource groups (and any similar things I am forgetting) from within the Access Controls pages dependent on a different permission (and maybe an irrevocable one, at least from within the Manager interface) than the permission(s) that control visibility elsewhere in Manager
• At the moment an access policy is about to be created, test to see if the user doing the creating will be affected by the policy and warn them ["You will lose access to X unless you either A) first create an ACL for X for your user group, or B) add yourself to the current user group. -cancel- or -proceed-]

Actually I think a combination of both would be best: warn them they will lose access if they proceed, but allow them to rectify the situation from the Access Controls pages regardless.

Also, perhaps the warnings could be controlled by some sort of "don’t bug me with stupid warnings, I know what I’m doing" system setting that could be turned off.

That’s my $.02 on the matter.

Quote from: jrotering at Jun 07, 2010, 09:58 AM

If you have any thoughts on how this could be improved (other than by better documenting the above points), I’d love to hear them.

• At the moment an access policy is about to be created, test to see if the user doing the creating will be affected by the policy and warn them ["You will lose access to X unless you either A) first create an ACL for X for your user group, or B) add yourself to the current user group. -cancel- or -proceed-]

I think this is a really great idea.

It would probably make your other suggestion unnecessary.

Could you file it using the Jira bugs and requests link at the top of this page so it won’t get lost in the shuffle?

(Feel free to file the other one too if you still think it’s necessary.)

Quote from: BobRay at Jun 07, 2010, 12:41 PM

I think this is a really great idea.

It would probably make your other suggestion unnecessary.

Could you file it using the Jira bugs and requests link at the top of this page so it won’t get lost in the shuffle?

Hang on before we file anything. Let’s discuss some more, because although that’s a wonderful idea, the implementation of such a feature is incredibly complex upon initial consideration. Let me think about this some more, and keep any and all ideas coming in the meantime.

Shows how much I know -- I figured that would be the easy one. 

I was thinking that you'd check the current user's access to the resource group or category, set the new rule, check the access to the resource group or category again, and issue the warning if there's a change and access will be lost.
[ed. note: BobRay last edited this post 12 years, 3 months ago.]

Quote from: BobRay at Jun 07, 2010, 01:03 PM

I was thinking that you’d check the current user’s access to the resource group or category, set the new rule, check the access to the resource group or category again, and issue the warning if there’s a change and access will be lost.

Since policies can be applied to multiple User Groups a user may be in (and soon directly to Users, as well as inherited from parent User Groups) with different authority levels and, in the case of Categories, can be inherited from parent Categories, there is no way to just "check the access" without running the checkPolicy() function in the proper "context", which would require all the data to already exist in the database and in the user session, etc.

I’m sure we can find a reasonable and practical solution though.

Maybe initially you could just throw a generic warning that doesn’t do any actual checking, just describes what might happen if the proper care isn’t taken. That would have been enough to probably save me from shooting myself in the foot.

Great to hear about the user group and category inheritance stuff that is coming. I’m sure I’ll be using those features.

I had such problem. No one category was displayed.
Just found out it`s cause. Table "modx_categories" was crashed. After repair all became fine
So check out your db, maybe it will help you

This saved me. Bookmarked too