Controlling the locations before/after publishing

Next topic

Author	Message
Piotrek Karaś	Tuesday 11 March 2008 10:11:51 pm I've got a question to the regarding information presented in the documentation: http://ez.no/doc/ez_publish/user_manual/4_0/daily_tasks/publishing_at_multiple_locations <i>In order to avoid possible conflicts when an object is edited by multiple users at the same time, the system will no longer allow to change locations via the object edit interface except the first object's version. This means that you can control locations when creating a new object but not when editing an existing one. However, it is still possible to modify location(s) of existing objects using the locations window that is displayed when viewing an object.</i> What conflicts are we talking about here and how serious are there? It seems to me that controlling locations is a process entirely independent of object layer: object modifications affect all locations, but do not change them; you can add/remove locations at any time without modifying (creating new version) object itself. So, why turning off the locations box/window in the edit view? Thanks for your thoughts on this, Piotrek -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu

Author

Message

Tuesday 11 March 2008 10:11:51 pm

I've got a question to the regarding information presented in the documentation:
http://ez.no/doc/ez_publish/user_manual/4_0/daily_tasks/publishing_at_multiple_locations

<i>In order to avoid possible conflicts when an object is edited by multiple users at the same time, the system will no longer allow to change locations via the object edit interface except the first object's version. This means that you can control locations when creating a new object but not when editing an existing one. However, it is still possible to modify location(s) of existing objects using the locations window that is displayed when viewing an object.</i>

What conflicts are we talking about here and how serious are there?

It seems to me that controlling locations is a process entirely independent of object layer: object modifications affect all locations, but do not change them; you can add/remove locations at any time without modifying (creating new version) object itself.

So, why turning off the locations box/window in the edit view?

Thanks for your thoughts on this,
Piotrek

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

eZ debug

Timing:	Jan 18 2025 22:11:20
Script start
Timing:	Jan 18 2025 22:11:20
Module start 'layout'
Timing:	Jan 18 2025 22:11:20
Module start 'content'
Timing:	Jan 18 2025 22:11:21
Module end 'content'
Timing:	Jan 18 2025 22:11:21
Script end

Main resources:

Total runtime	0.5290 sec
Peak memory usage	4,096.0000 KB
Database Queries	46

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0064	588.0469	152.6406
Module start 'layout'	0.0064	0.0038	740.6875	39.4922
Module start 'content'	0.0102	0.5174	780.1797	470.3438
Module end 'content'	0.5276	0.0014	1,250.5234	8.1250
Script end	0.5290		1,258.6484

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0054	1.0255	16	0.0003
Check MTime	0.0031	0.5811	16	0.0002
Mysql Total
Database connection	0.0008	0.1501	1	0.0008
Mysqli_queries	0.4848	91.6460	46	0.0105
Looping result	0.0004	0.0777	44	0.0000
Template Total	0.4925	93.1	2	0.2462
Template load	0.0040	0.7497	2	0.0020
Template processing	0.4885	92.3374	2	0.2442
Template load and register function	0.0001	0.0178	1	0.0001
states
state_id_array	0.0012	0.2223	1	0.0012
state_identifier_array	0.0007	0.1368	2	0.0004
Override
Cache load	0.0035	0.6622	12	0.0003
Sytem overhead
Fetch class attribute can translate value	0.0006	0.1040	1	0.0006
Fetch class attribute name	0.0006	0.1136	2	0.0003
XML
Image XML parsing	0.0004	0.0824	1	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0008	2	0.0000
General
dbfile	0.0020	0.3757	17	0.0001
String conversion	0.0000	0.0025	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
2	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 8 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs