ID: 373

Uploading Image From Image Relation Datatype (while editing content)

This feature request is part of Official Roadmap

Description

When editing a content object that has an attribute of the object relation datatype for images you have several clicks to upload the image in the media library first, then attach it to the current object (article).
This leads to both several clicks too much for the user and also a shift of context. The operation today consists of:
* Navigating to the right location in the media library
* Uploading an image and tagging it
* Enter the article editing interface
* Search for an image in the "add related object" field
* Attach image
The operation should be more similar to the one when adding an image in OE.
* Click upload image
* Choose location (dropdown?)
* Choose local file
* Ok
* File is automatically uploaded in the right location and added as a relation to the current object.
This is a daily operation for content editors and takes up much time if they want to have a nicely categorized media library and re-use the images in articles as front-page images or thumbnails (i.e. not uploading in the XML Text with OE).

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 15 2025 03:41:41
Script start
Timing: Jan 15 2025 03:41:41
Module start 'layout'
Timing: Jan 15 2025 03:41:41
Module start 'content'
Timing: Jan 15 2025 03:41:41
Module end 'content'
Timing: Jan 15 2025 03:41:41
Script end

Main resources:

Total runtime0.1199 sec
Peak memory usage6,144.0000 KB
Database Queries50

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0049 686.1719183.7188
Module start 'layout' 0.00490.0024 869.890652.6172
Module start 'content' 0.00730.1112 922.50782,139.5859
Module end 'content' 0.11850.0014 3,062.093870.7813
Script end 0.1199  3,132.8750 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00484.0386150.0003
Check MTime0.00121.0246150.0001
Mysql Total
Database connection0.00060.505110.0006
Mysqli_queries0.053844.8510500.0011
Looping result0.00030.2825480.0000
Template Total0.089774.820.0448
Template load0.00322.650620.0016
Template processing0.086572.108620.0432
Template load and register function0.00141.160510.0014
states
state_id_array0.00141.133910.0014
state_identifier_array0.00120.980420.0006
Override
Cache load0.00282.3209170.0002
Sytem overhead
Fetch class attribute name0.00161.367510.0016
class_abstraction
Instantiating content class attribute0.00000.004210.0000
General
dbfile0.00080.6973110.0001
String conversion0.00000.005040.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfeature_request/full.tplextension/community_design/design/suncana/override/templates/feature_request/full.tplEdit templateOverride template
1content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
1content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
1content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 5
 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs