Front editing and "inline" content

Previous topic

Extensions

Next topic

Author	Message
Sébastien Antoniotti	Wednesday 09 February 2011 8:16:55 am Hi ! I would like to know how some of you set up the administration (add, edit, delete) of images displayed into galleries when the user is logged on the frontoffice (with the ezwebin toolbar of course). For example, on a page if we have a photo gallery where the zoom is provided by a lightbox, the url of the full view of the image is never accessible. Thus, we can not use the ezwebin toolbar to edit or delete images in the gallery. Same goes for adding images, if images are placed in a folder under the page like this ... Home - My gallery (folder or gallery instance) ---- Image 1 (image) ---- Image 2 (image) ---- Picture N (image) ... we do not have access to the node My Gallery to created new images (still from the ezwebin toolbar). There is the possibility to modify the template that displays the gallery to place under it a link to the full view of "My gallery" only when a user is logged-in but it seems not very user friendly for editors ... Thanks in advance for your tips ! eZ Publish Freelance web : http://www.webaxis.fr
Peter Keung	Wednesday 09 February 2011 8:40:25 am In cases such as this, we have a separate "webin" siteaccess. Then, we can create an editor-specific full view override template for the special container classes. The template lists the children, even with edit buttons next to them if necessary. To preserve the ability for editors to see what their content is going to look like, they can always use the preview functionality and select a different siteaccess. http://www.mugo.ca Mugo Web, eZ Partner in Vancouver, Canada
Sébastien Antoniotti	Thursday 10 February 2011 1:04:56 am Hi Peter and thanks for this tips ! I'll think about an adaptation of this solution because I'm working on a website factory and I wanted to avoid to duplicate the siteaccesses for each site if possible... eZ Publish Freelance web : http://www.webaxis.fr

Author

Message

Sébastien Antoniotti

Wednesday 09 February 2011 8:16:55 am

Hi !

I would like to know how some of you set up the administration (add, edit, delete) of images displayed into galleries when the user is logged on the frontoffice (with the ezwebin toolbar of course).

For example, on a page if we have a photo gallery where the zoom is provided by a lightbox, the url of the full view of the image is never accessible.

Thus, we can not use the ezwebin toolbar to edit or delete images in the gallery.
Same goes for adding images, if images are placed in a folder under the page like this ...

Home
- My gallery (folder or gallery instance)
---- Image 1 (image)
---- Image 2 (image)
---- Picture N (image)

... we do not have access to the node My Gallery to created new images (still from the ezwebin toolbar).

There is the possibility to modify the template that displays the gallery to place under it a link to the full view of "My gallery" only when a user is logged-in but it seems not very user friendly for editors ...

Thanks in advance for your tips !

eZ Publish Freelance
web : http://www.webaxis.fr

Peter Keung

Wednesday 09 February 2011 8:40:25 am

In cases such as this, we have a separate "webin" siteaccess. Then, we can create an editor-specific full view override template for the special container classes. The template lists the children, even with edit buttons next to them if necessary. To preserve the ability for editors to see what their content is going to look like, they can always use the preview functionality and select a different siteaccess.

http://www.mugo.ca
Mugo Web, eZ Partner in Vancouver, Canada

Sébastien Antoniotti

Thursday 10 February 2011 1:04:56 am

Hi Peter and thanks for this tips !

I'll think about an adaptation of this solution because I'm working on a website factory and I wanted to avoid to duplicate the siteaccesses for each site if possible...

eZ Publish Freelance
web : http://www.webaxis.fr

eZ debug

Timing:	Jan 18 2025 03:07:45
Script start
Timing:	Jan 18 2025 03:07:45
Module start 'layout'
Timing:	Jan 18 2025 03:07:45
Module start 'content'
Timing:	Jan 18 2025 03:07:46
Module end 'content'
Timing:	Jan 18 2025 03:07:46
Script end

Main resources:

Total runtime	0.4190 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.0047	587.9219	152.6250
Module start 'layout'	0.0047	0.0023	740.5469	39.4688
Module start 'content'	0.0070	0.4104	780.0156	552.3516
Module end 'content'	0.4174	0.0015	1,332.3672	12.1563
Script end	0.4189		1,344.5234

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	0.6847	16	0.0002
Check MTime	0.0012	0.2792	16	0.0001
Mysql Total
Database connection	0.0007	0.1673	1	0.0007
Mysqli_queries	0.3731	89.0393	57	0.0065
Looping result	0.0007	0.1641	55	0.0000
Template Total	0.3938	94.0	2	0.1969
Template load	0.0020	0.4750	2	0.0010
Template processing	0.3918	93.5061	2	0.1959
Template load and register function	0.0001	0.0193	1	0.0001
states
state_id_array	0.0008	0.1838	1	0.0008
state_identifier_array	0.0007	0.1645	2	0.0003
Override
Cache load	0.0016	0.3874	24	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.1491	2	0.0003
Fetch class attribute name	0.0012	0.2921	5	0.0002
XML
Image XML parsing	0.0010	0.2439	2	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0020	6	0.0000
General
dbfile	0.0010	0.2433	23	0.0000
String conversion	0.0000	0.0017	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
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	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: 15 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs