Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Site with page amount > 1000


Go to End


9 Posts   3763 Views

Avatar
martimiz

Forum Moderator, 1391 Posts

8 February 2010 at 10:42am

Hi all,

The way I read Hierarchy, it looks like Silverstripe first tries to mark at least 30 pages for loading. It starts by traveling the first level, then al pages on the second, then the third, untill all or at least 30 pagenodes are collected - or even more, since it doesn't stop halfway between sibblings. Depending on how a site is build, only the first two levels could be marked, but it could also include say two submenus on the third level or even go up into the fourth.

For each page marked, SilverStripe finds out if it has children, cause then it needs an 'expanded' icon. All marked pages are loaded first, all others via ajax on request.

So I was thinking, theoretically, if you'd set the nr of pages to mark to say 2 or 3, instead of 30, only the first complete level would be preloaded. It would then of course take an Ajax call for each and every submenu.

I have, of course,no idea of any other implications, but I'd sure like to know what happens on a large (test!!!) site... I did try 850 pages, but on my server they load really fast anyway... Could it be a way of balancing the load? Find the $minCount param in Hierarchy method markPartialTree().

In 2.4beta1 there are a couple of changes to the procedure...

Go to Top