Comments on: The maximum of Sitecore items? At least a million!

By: Sasha

Sasha — Mon, 18 Jul 2011 20:42:31 +0000

P.S. Oops… got filtered out… as for #1: “Query.MaxItems”
Search for that in web.config

Sasha

By: Sasha

Sasha — Mon, 18 Jul 2011 20:40:56 +0000

Hi Another Sitecore Developer.

1) Number of items in a query limitation: check your web.config setting:

2) As of the query you are using, I don’t think that Sitecore recommends using such a reference as “descendant::*”

http://sitecorejohn.wordpress.com/2010/01/11/sitecore-best-practices-presentation-coding-and-configuration/

Make use of Caching.

I hope it helps!
Sasha

By: Another Sitecore developer

Another Sitecore developer — Thu, 09 Jun 2011 18:07:08 +0000

Agree with “Sitecore Developer”. We were 2 working on a company that uses Sitecore for it’s corporate website. The other guy quit 4 months ago, and now i’m leaving too.
Don’t know if we are working with a bad implementation of the CMS or what, but it’s really “heavy” to work with Sitecore.

Right now I’m looking why I cant list more than 100 sub-items on the same page. I’m using axes queries:
Item[] items;
string strQuery = “/sitecore/content/Another Site/descendant::*[@@templatename='Video Page']“;
items = Sitecore.Context.Item.Axes.SelectItems(strQuery);

Video Page’s are placed in sub-folders of “Another Site”. Each folder with no more than 10 items.

¿Any clue?

By: Sitecore developer

Sitecore developer — Tue, 20 May 2008 22:36:09 +0000

Yes, but in real life you can’t use sitecore with too many items. The more big the solution is the more slow the backend. And if you put some event handlers than you just got an useless sitecore backend where it takes half an hour to publish or 10 minutes to edit an item. Developement is really slow and time consuming with sitecore, and I’ve heard about a lot of developers changing their job because of that..