Multiple section problem. Any help?

Previous topic

Setup & design

Next topic

Author	Message
werner xaver	Wednesday 19 May 2004 12:32:32 am Hi, presently, i am evaluating the possibilities of eZ publish version 3.3-4. What i want to have is a way to store content objects in a non-readable section that only editors or admins have access to. Random contents then are to be published in various other locations in different sections that individual usergroups can access and read. The problem is that the content object in an additional location in another section does not become readable for the desired group although it is given the proper rights / roles. Can anyone show me a way out of this dilemma ? Can this be done with eZ publish ? Thanks in advance for any ideas regards werner
Mark Marsiglio	Wednesday 19 May 2004 8:33:45 pm Is it necessary to use the multiple location option to publish the content? It seems that one way might be to just move the content to a publicly visible section rather than to add a location. Alternately, it make work to add a second location and then to assign that one the as the main location. Either way, unless the object picks up the section of its new parent folder, it will not display. http://www.thinkcreative.com Turning Ideas Into Strategic Solutions

Author

Message

werner xaver

Wednesday 19 May 2004 12:32:32 am

Hi,

presently, i am evaluating the possibilities of eZ publish version 3.3-4.

What i want to have is a way to store content objects in a non-readable section that only editors or admins have access to.
Random contents then are to be published in various other locations in different sections that individual usergroups can access and read.

The problem is that the content object in an additional location in another section does not become readable for the desired group although it is given the proper rights / roles.

Can anyone show me a way out of this dilemma ?
Can this be done with eZ publish ?

Thanks in advance for any ideas

regards werner

Mark Marsiglio

Wednesday 19 May 2004 8:33:45 pm

Is it necessary to use the multiple location option to publish the content? It seems that one way might be to just move the content to a publicly visible section rather than to add a location. Alternately, it make work to add a second location and then to assign that one the as the main location.

Either way, unless the object picks up the section of its new parent folder, it will not display.

http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions

eZ debug

Timing:	Jan 18 2025 19:29:50
Script start
Timing:	Jan 18 2025 19:29:50
Module start 'layout'
Timing:	Jan 18 2025 19:29:50
Module start 'content'
Timing:	Jan 18 2025 19:29:50
Module end 'content'
Timing:	Jan 18 2025 19:29:50
Script end

Main resources:

Total runtime	0.0159 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.0067	588.0156	152.6250
Module start 'layout'	0.0067	0.0027	740.6406	39.4453
Module start 'content'	0.0094	0.0042	780.0859	89.3359
Module end 'content'	0.0137	0.0022	869.4219	30.3047
Script end	0.0159		899.7266

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	17.8995	14	0.0002
Check MTime	0.0013	8.0883	14	0.0001
Mysql Total
Database connection	0.0012	7.3715	1	0.0012
Mysqli_queries	0.0029	18.2789	3	0.0010
Looping result	0.0000	0.0825	1	0.0000
Template Total	0.0018	11.4	1	0.0018
Template load	0.0010	6.4089	1	0.0010
Template processing	0.0008	4.9244	1	0.0008
Override
Cache load	0.0007	4.5600	1	0.0007
General
dbfile	0.0004	2.2388	8	0.0000
String conversion	0.0000	0.0450	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