Paginate the dynamic Content Structure Menu

Next topic

Author	Message
Erik Weinmaster	Tuesday 12 October 2010 6:54:55 am One thing I always notice about the Content Structure is the fact that its never separated into more than one page. I have my own side project with ez publish 4.3 (so no, I haven't done the upgrade yet), but I notice that after roughly 175 entries in the content structure menu, it begins cutting them off. I see that the sub items for every node has the limiting factor of 10, 25, and 50. Why not do the same thing for the left hand menu? Of course you probably couldn't do the same (offset)/some_number module request, but what about storing this data in the session and thus the user has it for their duration? Or perhaps including this feature, but by default its disabled?
Heath	Tuesday 12 October 2010 4:26:04 pm Hello Erik, I have to say I disagree with this idea. It strikes as a bad idea since the content structure menu is displaying a tree of content data not a list. I think it would be better for you (on your site) to limit the number of content objects displayed in the menu (by class identifier for example, see: settings/contentstructuremenu.ini ) which parent is the root node. Cheers, Heath Brookins Consulting \| http://brookinsconsulting.com/ Certified \| http://auth.ez.no/certification/verify/380350 Solutions \| http://projects.ez.no/users/community/brookins_consulting eZpedia community documentation project \| http://ezpedia.org

Author

Message

Tuesday 12 October 2010 6:54:55 am

One thing I always notice about the Content Structure is the fact that its never separated into more than one page. I have my own side project with ez publish 4.3 (so no, I haven't done the upgrade yet), but I notice that after roughly 175 entries in the content structure menu, it begins cutting them off. I see that the sub items for every node has the limiting factor of 10, 25, and 50. Why not do the same thing for the left hand menu? Of course you probably couldn't do the same (offset)/some_number module request, but what about storing this data in the session and thus the user has it for their duration? Or perhaps including this feature, but by default its disabled?

Heath

Tuesday 12 October 2010 4:26:04 pm

Hello Erik,

I have to say I disagree with this idea. It strikes as a bad idea since the content structure menu is displaying a tree of content data not a list.

I think it would be better for you (on your site) to limit the number of content objects displayed in the menu (by class identifier for example, see: settings/contentstructuremenu.ini ) which parent is the root node.

Cheers,

Heath

Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org

eZ debug

Timing:	Jan 18 2025 04:09:16
Script start
Timing:	Jan 18 2025 04:09:16
Module start 'layout'
Timing:	Jan 18 2025 04:09:16
Module start 'content'
Timing:	Jan 18 2025 04:09:17
Module end 'content'
Timing:	Jan 18 2025 04:09:17
Script end

Main resources:

Total runtime	0.8237 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.0060	589.4766	152.6406
Module start 'layout'	0.0060	0.0033	742.1172	39.4844
Module start 'content'	0.0093	0.8132	781.6016	520.9922
Module end 'content'	0.8225	0.0012	1,302.5938	8.1250
Script end	0.8237		1,310.7188

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.4418	16	0.0002
Check MTime	0.0014	0.1751	16	0.0001
Mysql Total
Database connection	0.0008	0.0935	1	0.0008
Mysqli_queries	0.7822	94.9577	54	0.0145
Looping result	0.0006	0.0676	52	0.0000
Template Total	0.7935	96.3	2	0.3967
Template load	0.0026	0.3101	2	0.0013
Template processing	0.7909	96.0185	2	0.3954
Template load and register function	0.0001	0.0158	1	0.0001
states
state_id_array	0.0003	0.0386	1	0.0003
state_identifier_array	0.0005	0.0646	2	0.0003
Override
Cache load	0.0020	0.2488	11	0.0002
Sytem overhead
Fetch class attribute can translate value	0.0009	0.1087	2	0.0004
Fetch class attribute name	0.0009	0.1141	3	0.0003
XML
Image XML parsing	0.0009	0.1058	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0010	3	0.0000
General
dbfile	0.0008	0.0918	17	0.0000
String conversion	0.0000	0.0012	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