Understanding Image/Thumbnail functionnalities ? Help :)

Previous topic

Setup & design

Next topic

Author	Message
H-Works Agency	Saturday 16 April 2005 6:53:23 am Hi all, After a lot of search in the doc, i am still not understanding the way EZP 3.5+ handles image compression and thumbnailing. When does the compression process occurs ? Where thoses files are stored ? What is the difference between var/sitename/../images and images-versionned ? Why entering new AliasList[] description in my siteaccess/../image.ini doesn't have the effect of building each AliasList[] entrie during admin image upload ? Does thoes compressions and multiple copies described in siteacess/../image.ini occurs when the image is uploaded through the admin OR when the specific AliasList[] entries are called in public template ? Thanx all - Martin EZP is Great
Jan Borsodi	Wednesday 27 April 2005 12:48:30 am > When does the compression process occurs ? Where thoses > files are stored ? Do you mean compression or scaling? The compression is handled by either ImageMagick or the GD extension and depends on the image format (some doesn't have compression). Scaling is done when calling the ImagMagick executable (or in PHP code when using GD). These files are stored inside the <i>var/storage</i> directory in a subdirectory depending on if it is in a version or not. > What is the difference between var/sitename/../images and > images-versionned ? <i>/images</i> is used when the object is published, it will place the image in a path taken from the URL alias of the object. <i>/images-versioned</i> is used when editing an object (ie a specific version), at that time the path is not known and the image is stored only under the object/version combination. > Why entering new AliasList[] description in my > siteaccess/../image.ini doesn't have the effect of > building each AliasList[] entrie during admin image > upload ? I'm not sure what you mean here. Which description are you referring to? Do you mean that the list of aliases is not updated when uploading the new image? > Does thoes compressions and multiple copies described in > siteacess/../image.ini occurs when the image is uploaded > through the admin OR when the specific AliasList[] entries > are called in public template ? Scaling is done on the original image when it is uploaded if it is defined, if not it is only moved. For the rest of the aliases it is done the first time it is accessed by the template or PHP code. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
H-Works Agency	Wednesday 27 April 2005 9:15:53 am I understand now the way EZP handle images. AliasList[] entries are build (either by ImageMagic \| GD) first time its called by a template (either in admin \| public site). Thanks a lot for those infos. EZP is Great

Author

Message

H-Works Agency

Saturday 16 April 2005 6:53:23 am

Hi all,

After a lot of search in the doc, i am still not understanding the way EZP 3.5+ handles image compression and thumbnailing.

When does the compression process occurs ? Where thoses files are stored ?

What is the difference between var/sitename/../images and images-versionned ?

Why entering new AliasList[] description in my siteaccess/../image.ini doesn't have the effect of building each AliasList[] entrie during admin image upload ?

Does thoes compressions and multiple copies described in siteacess/../image.ini occurs when the image is uploaded through the admin OR when the specific AliasList[] entries are called in public template ?

Thanx all - Martin

EZP is Great

Jan Borsodi

Wednesday 27 April 2005 12:48:30 am

> When does the compression process occurs ? Where thoses
> files are stored ?

Do you mean compression or scaling?
The compression is handled by either ImageMagick or the GD extension and depends on the image format (some doesn't have compression).

Scaling is done when calling the ImagMagick executable (or in PHP code when using GD).
These files are stored inside the var/storage directory in a subdirectory depending on if it is in a version or not.

> What is the difference between var/sitename/../images and
> images-versionned ?
/images is used when the object is published, it will place the image in a path taken from the URL alias of the object.
/images-versioned is used when editing an object (ie a specific version), at that time the path is not known and the image is stored only under the object/version combination.

> Why entering new AliasList[] description in my
> siteaccess/../image.ini doesn't have the effect of
> building each AliasList[] entrie during admin image
> upload ?
I'm not sure what you mean here. Which description are you referring to?
Do you mean that the list of aliases is not updated when uploading the new image?

> Does thoes compressions and multiple copies described in
> siteacess/../image.ini occurs when the image is uploaded
> through the admin OR when the specific AliasList[] entries
> are called in public template ?

Scaling is done on the original image when it is uploaded if it is defined, if not it is only moved.
For the rest of the aliases it is done the first time it is accessed by the template or PHP code.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

H-Works Agency

Wednesday 27 April 2005 9:15:53 am

I understand now the way EZP handle images.

AliasList[] entries are build (either by ImageMagic | GD) first time its called by a template (either in admin | public site).

Thanks a lot for those infos.

EZP is Great

eZ debug

Timing:	Jan 18 2025 11:13:48
Script start
Timing:	Jan 18 2025 11:13:48
Module start 'layout'
Timing:	Jan 18 2025 11:13:48
Module start 'content'
Timing:	Jan 18 2025 11:13:49
Module end 'content'
Timing:	Jan 18 2025 11:13:49
Script end

Main resources:

Total runtime	0.9279 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0054	589.2734	152.6563
Module start 'layout'	0.0054	0.0047	741.9297	39.4922
Module start 'content'	0.0101	0.9167	781.4219	552.5781
Module end 'content'	0.9268	0.0011	1,334.0000	12.1094
Script end	0.9279		1,346.1094

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.3643	16	0.0002
Check MTime	0.0014	0.1471	16	0.0001
Mysql Total
Database connection	0.0010	0.1036	1	0.0010
Mysqli_queries	0.8722	93.9988	57	0.0153
Looping result	0.0006	0.0637	55	0.0000
Template Total	0.8955	96.5	2	0.4477
Template load	0.0022	0.2419	2	0.0011
Template processing	0.8932	96.2603	2	0.4466
Template load and register function	0.0001	0.0108	1	0.0001
states
state_id_array	0.0013	0.1438	1	0.0013
state_identifier_array	0.0007	0.0801	2	0.0004
Override
Cache load	0.0021	0.2224	40	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.0957	2	0.0004
Fetch class attribute name	0.0022	0.2335	5	0.0004
XML
Image XML parsing	0.0010	0.1109	2	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0012	6	0.0000
General
dbfile	0.0008	0.0856	24	0.0000
String conversion	0.0000	0.0009	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
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
9	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
7	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 24 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs