Roles and Permission - EZCrew Please help

«

Previous topic

|

|

Next topic

»

Author	Message
John Smith	Wednesday 22 February 2006 9:57:36 am hi there, Hope someone can help me in getting the functionality given below: 1. Administrator can create a "Forum/Discussion Topic" from the administration interface of the website. 2. After the administrator created a "Forum/Discussion Topic", it gets visible to all the user of the public website. In other words, the public can now see the "Forum/Discussion Topic". 3. Now anyone from the public can post a "Forum/Discussion Topic Reply" to that "Forum/Discussion Topic", but the "Forum/Discussion Topic Reply" has to be approved by the administrator before it gets visible to the public. 4. Users can't edit their replies. Thanks in advance John
Łukasz Serwatka	Thursday 23 February 2006 1:03:13 am Hi John, 1. You will need to create new police for "normal" users: Module Function Limitation content create Class( Forum message ) Parent class( Discussion Topic ) Module Function Limitation content edit Class( Forum message ) Parent class( Discussion Topic ) 2. Display only "create new reply" form to normal users. Not edit form. 3. Setup Workflow with Approve event. http://ez.no/doc/ez_publish/technical_manual/3_6/reference/workflow_events/approve Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
John Smith	Thursday 23 February 2006 1:41:00 am thanks for your kind help. I will try what you said. Can you please explain the second point in more detail - like how to hide the edit form. In the meantime please help me in another point if possible. Here in my website I want some kind of feedbacks from the anonymous users on the article already published by the administrator. But obviously the feedback/comments has to be approved by the administrator before it get visible to the public underneath that article. Thanks in advance. Cheers.
Łukasz Serwatka	Thursday 23 February 2006 1:48:47 am John, use Approve workflow event. Here you can read more: http://ez.no/doc/ez_publish/technical_manual/3_6/reference/workflow_events/approve and take this tutorial (present your problem): http://ez.no/products/ez_publish/documentation/building_an_ez_publish_site/the_guestbook/creating_a_workflow Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
John Smith	Thursday 23 February 2006 2:00:53 am In the guest book example, you are dealing with one folder and entries. Can i do the same thing with the number of articles and their relevant entries. In your previous reply regarding discussion topics, you said "Display only "create new reply" form to normal users. Not edit form." Can you please make this point more clear. Cheers.
Łukasz Serwatka	Thursday 23 February 2006 2:16:14 am Can i do the same thing with the number of articles and their relevant entries. Yes, you can define in approve event section which will be affected by approve mechanism. Lets say you have section News, someone will publish comment in this section then administrator must approve it. It doesn't matter if this is one folder or many, but everything must be around section specified in workflow event. Check on template level, if user can create object or not then display "Post reply" button. {if $node.object.can_crate} <form method="post" action="/content/action"> <input type="hidden" name="NodeID" value="{$node.node_id}" /> <input type="hidden" name="ClassID" value="CLASS_ID_OF_FORUM_MSG" /> <input class="button" type="submit" name="NewButton" value="Post reply" /> </form> {/if} Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
John Smith	Thursday 23 February 2006 5:09:58 am thanks Lukasz for you kind help. You are really doing good job by helping the community. cheers

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 18 2025 16:25:58
Script start
Timing:	Jan 18 2025 16:25:58
Module start 'layout'
Timing:	Jan 18 2025 16:25:58
Module start 'content'
Timing:	Jan 18 2025 16:25:58
Module end 'content'
Timing:	Jan 18 2025 16:25:58
Script end

Main resources:

Total runtime	0.0191 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0065	588.0078	152.6250
Module start 'layout'	0.0065	0.0039	740.6328	39.4453
Module start 'content'	0.0104	0.0064	780.0781	97.4609
Module end 'content'	0.0168	0.0022	877.5391	38.3047
Script end	0.0190		915.8438

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	17.0029	14	0.0002
Check MTime	0.0012	6.1264	14	0.0001
Mysql Total
Database connection	0.0010	5.3801	1	0.0010
Mysqli_queries	0.0029	15.0966	3	0.0010
Looping result	0.0000	0.2038	1	0.0000
Template Total	0.0017	9.2	1	0.0017
Template load	0.0010	5.2639	1	0.0010
Template processing	0.0007	3.8738	1	0.0007
Override
Cache load	0.0007	3.5863	1	0.0007
General
dbfile	0.0003	1.6988	8	0.0000
String conversion	0.0000	0.0538	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs