I’ve read a couple of other posts somewhat regarding this, but they didn’t really clarify (for me anyway) how to accomplish this.
I have a site user (not a web user) who’s been given the role of "Site Editor" - a lot like the administrator, but with several things "turned off" such as template editing. Anyway, as an administrator, I can launch the site from the manager and see the "manage pictures" button. Great! I’d like to for certain users (or site user roles) to have the same ability as currently they do not. How can I get that going?
Thanks! And thanks for this awesome script!
If the manager user has rights to edit the document, he should see the manage pictures button.
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
Yeah, that would seem logical, but it doesn’t work. The Site Editor role has rights to edit all documents... What am I missing? Is there a setting for it somewhere?
Are the documents assigned to the site editors document group?
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
I’m not 100% sure, but I think that the documents need to be in a documen group that belongs to the site editors usergroup.. don’t have time to check the code right now.. Or are you perhaps logged in at the front end at the same time? there is some bugs in that situation, there is a thread with a fix around this sub forum somewhere.
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
I’m actually having this problem as well. It is definitely a problem from a useability standpoint.
I created a new role that has access to edit all pages (by default), and the user is fully able to go in and edit the content on the page (without setting up a relationship in the document permissions manager). It only makes sense that if the user can physically edit the page that they should be able to manage the gallery as well. From a user standpoint, either newly created roles shouldn’t be able to edit documents until they are explicitly added to the document permissions, or maxi gallery pages should be maintainable without doing so.
Yes, I need to fix this at some point, but not going to happen very soon.. I’m on a work trip for the rest of the year and development on this will probably slow down littlebit and this "bug" is not very high on my priority list.. but its a bug indeed. If you or someone else like to look into this, it’s the checkPermissions function in maxigallery class that needs to be fixed. Currently it looks for the permissions on document group basis.
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
Just came back home this weekend.. good that you remainded me about this as I had forgotten it, because it’s not on the
Trac site.. I’ll look at it and get it fixed for next release..
"He can have a lollipop any time he wants to. That's what it means to be a programmer."