|
Author
|
Message
|
|
Alan Sparkes
|
Monday 13 October 2003 9:29:49 am
I have been looking at Ezpub3.2 on Win XP .
I have added a user fred to editors role and setup workflow and trigers as suggested at sdk [http://pubsvn.ez.no/sdk/] There doesnt seem to be a big difference. What I think I am doing is letting user 'fred' of editor group publish articles in Standard Section in the folder/node called news. I have gone thru SDK as suggested, assigned editor grp and fred as individual [is necessary?]
Problem:
Fred can read [cos i added read permission] but he cannot post an article. Settings are:
user login *
content read *
content create Class( Article ) , Section( Standard section ) Why cant Fred create articles? alan
|
|
Marco Zinn
|
Monday 13 October 2003 11:10:37 am
Hi Alan,
hm, should work.
First: You should not need workflows and triggers in your case. Maybe you should disable this for now. If you assigned some workflow to the "publish" triggers, set them to "no workflow".
Workflows only work and progress, when you set up cron jobs (or run "runcronsjobs.php" manually). If you did not yet do that, you publishing worflow probably stucks somewhere. If this does not work, change the last permission to "content create *" You shouldn't need to assign the role to an indivual user, if you assign it to his group.
Marco
http://www.hyperroad-design.com
|
|
Frode Marton Meling
|
Tuesday 14 October 2003 1:38:29 am
PS! Remember that the user also needs edit rights!! The publishing in eZ Publish is done by redirecting. So when you create a new node (Pressing create), the node is created on the next web page and then automatically (instant) redirected to edit mode on that node. Frode
|
|
Alan Sparkes
|
Tuesday 14 October 2003 12:42:04 pm
Quote:
You should not need workflows and triggers in your case Mmm. I thought the idea of workflows was that editors could login, only see what you wanted them to see, and only submit for publishing those content objects setup in the workflow for the editors group. I am testing EZPublish to see if it can allow an editor to log in and submit but not publish. And as far as I can tell, it doesnt work. I am using sepearate browsers [IE6 and Mozilla 1.4] in order to test this. I will try deleting the workflow and triggers to see if this allows Fred [see above] to submit. If I am on the wrong track here with user submissions then please someone steer me in the right direction. Thank you... alans
|
|
Alan Sparkes
|
Tuesday 14 October 2003 12:47:42 pm
If as I am trying to do create a user called fred who can submit articles should he login at the user site or the admin site? alans
|
|
Paul Borgermans
|
Tuesday 14 October 2003 1:29:40 pm
The admin site is in fact the user side and reverse in the sense that they are both a "siteaccess" with a different "design". The admin site is just a predefined siteaccess which lets you do a small part of ez functionality in a nice interface, geared towards admins. What I do is let users have access to certain admin functions ... but they remain in the user siteaccess. -paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Alan Sparkes
|
Tuesday 14 October 2003 1:40:40 pm
Ok I have taken workflow out, given fred create * * priveleges and he still can't create! Has anyone else experienced this? alan-s PostNuke you are forgiven!!!
|
|
Paul Borgermans
|
Tuesday 14 October 2003 2:14:51 pm
Alan, This is indeed not enough: you need to add an edit policy to the role: content edit (Class Article), Section (Standard section) A single edit policy is also not enough to create items, but this enables what it supposes to do: editing existing items. Don't know to call this a feature or a bug :) hth -paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Paal Are Solberg
|
Wednesday 22 October 2003 12:13:21 pm
Remove this entry(see answers above)
|