package installation

Next topic

Author	Message
Pascal France	Saturday 22 July 2006 11:08:00 am Hi, I would like to understand what does exactly the fourth step of a "Content object packages" installation described here: http://ez.no/doc/ez_publish/technical_manual/3_8/features/packages/installing_packages I tried to changed the "Top node placement" of a package (I did two installations of the same package - removing it and its elements after the first installation) and I don't understand what the difference between a "Top node placement" and another one. Regards Pascal Ce qui embellit le désert c'est qu'il cache un puits... quelque part... (A. de Saint-Exupéry) - http://luxpopuli.fr/eZ-Publish
Svitlana Shatokhina	Wednesday 16 August 2006 2:08:44 am Hi, This step allows you to choose where the installed objects will be located. Example: - Create a folder called "My products". - Install a package that contains some products and select the "My products" folder as a top node placement at the 4-th step. The system will put all products installed from this package under this folder. If this functionality does not work as described, please post a bugreport at http://ez.no/community/bugs Best regards, Sveta P.S. a bugreport related to this theme - http://ez.no/bugs/view/8836

Author

Message

Saturday 22 July 2006 11:08:00 am

Hi,

I would like to understand what does exactly the fourth step of a "Content object packages" installation described here:

http://ez.no/doc/ez_publish/technical_manual/3_8/features/packages/installing_packages

I tried to changed the "Top node placement" of a package (I did two installations of the same package - removing it and its elements after the first installation) and I don't understand what the difference between a "Top node placement" and another one.

Regards

Pascal

Ce qui embellit le désert c'est qu'il cache un puits... quelque part... (A. de Saint-Exupéry) - http://luxpopuli.fr/eZ-Publish

Svitlana Shatokhina

Wednesday 16 August 2006 2:08:44 am

Hi,

This step allows you to choose where the installed objects will be located.

Example:

- Create a folder called "My products".
- Install a package that contains some products and select the "My products" folder as a top node placement at the 4-th step.

The system will put all products installed from this package under this folder.

If this functionality does not work as described, please post a bugreport at http://ez.no/community/bugs

Best regards,
Sveta

P.S.
a bugreport related to this theme - http://ez.no/bugs/view/8836

eZ debug

Timing:	Jan 18 2025 16:01:39
Script start
Timing:	Jan 18 2025 16:01:39
Module start 'layout'
Timing:	Jan 18 2025 16:01:39
Module start 'content'
Timing:	Jan 18 2025 16:01:39
Module end 'content'
Timing:	Jan 18 2025 16:01:39
Script end

Main resources:

Total runtime	0.0184 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.0066	587.9141	152.6250
Module start 'layout'	0.0066	0.0032	740.5391	39.4453
Module start 'content'	0.0098	0.0065	779.9844	89.2266
Module end 'content'	0.0163	0.0021	869.2109	30.3047
Script end	0.0184		899.5156

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	14.6105	14	0.0002
Check MTime	0.0011	6.1724	14	0.0001
Mysql Total
Database connection	0.0008	4.5277	1	0.0008
Mysqli_queries	0.0030	16.3031	3	0.0010
Looping result	0.0000	0.0763	1	0.0000
Template Total	0.0017	9.4	1	0.0017
Template load	0.0010	5.2109	1	0.0010
Template processing	0.0008	4.1304	1	0.0008
Override
Cache load	0.0007	3.5766	1	0.0007
General
dbfile	0.0012	6.3496	8	0.0001
String conversion	0.0000	0.0543	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