Uploaded Object default location

Next topic

Author	Message
Mihai007 Pop	Monday 26 November 2007 5:05:47 am When a user clicks on the attachment paperclip to upload a new image/file/etc..., there is an option to place it in a certain location. The options are: automatic, images, files, etc...! The nice thing about this when you upload it to an existing class (eg. article), the article itself is shown in the list. This means that all the images uploaded to this class will be placed as children of this class. However, when you first create a new class, the option is not shown for the new class. I understand that it is because the class has not been made yet. But I know that a draft has been created. This means that it can be temporarily associated to the draft before associated to the actual class when published. I just don't know where the uploaded files are placed once they have been placed in the "automatic" option. For a news site, this would work nice because a writer could write the document, upload the files, and show them in the article (all under one class). No back-and-fourths.
André R.	Monday 07 January 2008 6:48:34 am automatic are based on the settings defined in content.ini depending on the file you upload, bye default they end up in the media library. As for the storing as children before it's published, that's not currently easy since the object doesn't have have node assignment yet. Adding such a feature would probably involve storing the relations as drafts without a node, and add the node placement with a cronjob/ workflow when the object is published or in some way when you hit publish on the main object ( id's could be stored as session ). eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom

Author

Message

Monday 26 November 2007 5:05:47 am

When a user clicks on the attachment paperclip to upload a new image/file/etc..., there is an option to place it in a certain location.

The options are: automatic, images, files, etc...! The nice thing about this when you upload it to an existing class (eg. article), the article itself is shown in the list. This means that all the images uploaded to this class will be placed as children of this class.

However, when you first create a new class, the option is not shown for the new class. I understand that it is because the class has not been made yet. But I know that a draft has been created. This means that it can be temporarily associated to the draft before associated to the actual class when published.

I just don't know where the uploaded files are placed once they have been placed in the "automatic" option.

For a news site, this would work nice because a writer could write the document, upload the files, and show them in the article (all under one class). No back-and-fourths.

André R.

Monday 07 January 2008 6:48:34 am

automatic are based on the settings defined in content.ini depending on the file you upload, bye default they end up in the media library.

As for the storing as children before it's published, that's not currently easy since the object doesn't have have node assignment yet.

Adding such a feature would probably involve storing the relations as drafts without a node, and add the node placement with a cronjob/ workflow when the object is published or in some way when you hit publish on the main object ( id's could be stored as session ).

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

eZ debug

Timing:	Jan 18 2025 05:08:50
Script start
Timing:	Jan 18 2025 05:08:50
Module start 'layout'
Timing:	Jan 18 2025 05:08:50
Module start 'content'
Timing:	Jan 18 2025 05:08:51
Module end 'content'
Timing:	Jan 18 2025 05:08:51
Script end

Main resources:

Total runtime	0.5168 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0064	587.9219	152.6250
Module start 'layout'	0.0064	0.0029	740.5469	39.4609
Module start 'content'	0.0093	0.5059	780.0078	524.0781
Module end 'content'	0.5151	0.0016	1,304.0859	8.1563
Script end	0.5167		1,312.2422

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.6389	16	0.0002
Check MTime	0.0014	0.2639	16	0.0001
Mysql Total
Database connection	0.0012	0.2295	1	0.0012
Mysqli_queries	0.4705	91.0470	54	0.0087
Looping result	0.0006	0.1098	52	0.0000
Template Total	0.4846	93.8	2	0.2423
Template load	0.0022	0.4166	2	0.0011
Template processing	0.4825	93.3596	2	0.2412
Template load and register function	0.0002	0.0298	1	0.0002
states
state_id_array	0.0008	0.1587	1	0.0008
state_identifier_array	0.0009	0.1794	2	0.0005
Override
Cache load	0.0017	0.3373	13	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.1725	2	0.0004
Fetch class attribute name	0.0013	0.2587	3	0.0004
XML
Image XML parsing	0.0007	0.1391	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0015	3	0.0000
General
dbfile	0.0007	0.1398	17	0.0000
String conversion	0.0000	0.0021	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
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
2	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 7 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs