eZ Crew: How does the image uploading work?

Next topic

Author	Message
Jerry Jalava	Thursday 31 July 2003 4:17:10 am I would like to know how does the image upload work in ez... I know it uses few files (ie. ezimage.php,ezimagevariations.php,ezimagetype.php,image.php...) But how does it know when image is uploaded ie. through class? I tried to examine the code all around eZ, but couldn't find where the ezimage files get the command to process the image that I'm uploading from ie. my class witch has image in it... So, where do I activate the image uploading in my own module? I need to know, because I need image uploading to one of my modules (uses own database, not ezcontent one), and I would like to use the eZ's way to save the image to server... Thanks, Jerry
Jerry Jalava	Friday 01 August 2003 6:03:10 am I really need to know this... This is the key element that i still missing from my module... I can't finish my project without knowing this... :( I know that the real uploading happens in ezhttpfile.php -file, but if I would like to save something with it to the server, I need to know the Mimetype and mimecategory, which I get from the ezimage -files... So, how can I tell ezimage that I wan't this file to be saved... I have tried all kind of stuff, but without any progress. Please help... Thanks, Jerry

Author

Message

Thursday 31 July 2003 4:17:10 am

I would like to know how does the image upload work in ez... I know it uses few files (ie. ezimage.php,ezimagevariations.php,ezimagetype.php,image.php...)

But how does it know when image is uploaded ie. through class?

I tried to examine the code all around eZ, but couldn't find where the ezimage files get the command to process the image that I'm uploading from ie. my class witch has image in it...

So, where do I activate the image uploading in my own module?

I need to know, because I need image uploading to one of my modules (uses own database, not ezcontent one), and I would like to use the eZ's way to save the image to server...

Thanks,
Jerry

Jerry Jalava

Friday 01 August 2003 6:03:10 am

I really need to know this... This is the key element that i still missing from my module... I can't finish my project without knowing this... :(

I know that the real uploading happens in ezhttpfile.php -file, but if I would like to save something with it to the server, I need to know the Mimetype and mimecategory, which I get from the ezimage -files...

So, how can I tell ezimage that I wan't this file to be saved...
I have tried all kind of stuff, but without any progress.

Please help...

Thanks,
Jerry

eZ debug

Timing:	Jan 31 2025 03:44:14
Script start
Timing:	Jan 31 2025 03:44:14
Module start 'layout'
Timing:	Jan 31 2025 03:44:14
Module start 'content'
Timing:	Jan 31 2025 03:44:14
Module end 'content'
Timing:	Jan 31 2025 03:44:14
Script end

Main resources:

Total runtime	0.0242 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	588.2656	151.2266
Module start 'layout'	0.0057	0.0041	739.4922	220.7188
Module start 'content'	0.0098	0.0130	960.2109	997.7266
Module end 'content'	0.0228	0.0014	1,957.9375	29.9922
Script end	0.0242		1,987.9297

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	11.2861	14	0.0002
Check MTime	0.0011	4.4011	14	0.0001
Mysql Total
Database connection	0.0006	2.3400	1	0.0006
Mysqli_queries	0.0028	11.4310	3	0.0009
Looping result	0.0000	0.0582	1	0.0000
Template Total	0.0009	3.8	1	0.0009
Template load	0.0007	2.8861	1	0.0007
Template processing	0.0002	0.8723	1	0.0002
Override
Cache load	0.0005	2.0177	1	0.0005
General
dbfile	0.0012	5.0260	8	0.0002
String conversion	0.0000	0.0404	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