rights for publishing (done) an others rights

Hello

I’m estonished that their is nothing to grant (or not) publishers for publishing theires pages.

I’ve finded a bug in rights that do not function (or not as I read them) ... but I don’t know where to put a topic for them... this is with "allowed to modify" (hops it the good translation) and a nonsense with the right for "saving"

Edit : updated title to point others rights I discussed

A seperate publish privilege will be in next release.

The "can modify but can’t save" thing is really somehow strange You may wish to create an entry in the Bugtracker for that: http://modxcms.com/bugs/

It’s just a matter of the wording. "edit" or "modify" means you can open the code. "save" means you can save it. Kind of hard to change that now, since it’s really embedded in the system.

But the "can modify but can’t save" thing is still good to have.. so users like Susan can setup a demo site where users can view how the pages and snippets are set up, but not save anything..

Yeah, when I remember to pay for the domain registration on time

Publishing permissions is now in the latest trunk I believe.

Hello

Quote from: doze at Oct 12, 2006, 11:07 AM

But the "can modify but can’t save" thing is still good to have.. so users like Susan can setup a demo site where users can view how the pages and snippets are set up, but not save anything..

well that’s an argument.... I don’t think would be my choice (for demo, I would prefer a cron that put the site in it’s start state every 2 hours so that "Susan" could test from begenning to the top end), but I understand.

thanks for your explanation.

Quote from: rthrash at Oct 13, 2006, 01:57 PM

Publishing permissions is now in the latest trunk I believe.

where can I search a global info about this ?
I ask because... after tunning just a little my first test site, I arrived to the idea that every data (?) of the page should be permissioned :
* changing template
* web access and manager access
* everything with cache control
* changing a document to a directory or vice versa
...

I most certainly do not want to be resetting my site every two hours! That’s my remote working, demo, and tutorial site. Letting users look "under the hood" is a very useful part of the tutorials and demos.

piwaille, for such "basic" questions you can always ask the french forum, it might be less painful trying to explain what is not clear for you about roles and permissions in your native language

I’m still replying here ....
Thinking about the right to change template... I arrived to a state where the system I test in 0.9.5 lead to noway

may be I should make a post especialy for templating management ?

Well : my reflections :

When I create a directory, it is for holding documents... It is nice that, in the directory I can put a template that will be proposed for the documents....
btu on the other way, that directory is comuted as a document itself
let say the directory is called DIR and the docs are doc1, doc2

I create dir, it says that default template is T ...nice...
I create doc1 with the template T ... very nice
I create doc2 with the same tempalte T ... still nice

But not... when I surf on my site... if I click on the menu "dir" ... I would rather see an index...
So to build my index... i would change my template of dir in order the not see the TV I used on doc1 and doc2...
I may use something like "my first datagrid" ... so with a special template for displaying it ...
but if I do that, creating doc3, doc4 ... will become very painfull

So .... I think, default template (and templates rights) could be included in groups :
the group that is allowed to create documents in the dir directory should use the T template

Their is an other solution : doing like the site : when I make a directory, I could say that the index of this directory is document #... (doc0) which could be built by an admin with another template. use FirstChildRedicrect (I’m currently reading it... )

hop I can be understand