I think the issue is basically with load times. The first time you
view the page in SmartEdit, it will take a while to render. Once the
page is cached though, it is fast consecutive times. Opening the list
in SmartTree may take a long time and if your IIS server has small
timeouts, can cause an issue. Otherwise, I think that there should be
no problem with long lists.

On Jan 14, 9:07 am, redDolt <[email protected]> wrote:
> We have about 350 products on our website split between about 30
> product sub-lines. It quickly became necessary to have a way to look
> at them all at once without having to crawl the whole site. So i have
> a cms only page with all the product pages on one list. Works fine.
> Takes a sec to render in smarttree, but in smartedit its pretty
> snappy.
>
> We also have a similar section where we load in a bunch of pages for
> connecting media (for keywording purposes) to hold our operation and
> parts manuals. There are probably about 1.5x as many manuals as
> products (multiple languages, specialized books, etc). That also works
> fine.
>
> I believe when they say "might be issues" they've always meant numbers
> in the thousands. 10,000 jumps out at me for some reason, but it might
> just be because its a sexy number.
>
> On Jan 14, 7:51 am, abdn_webteam <[email protected]> wrote:
>
>
>
> > The title says it all.
>
> > We were told by our friendly neighbourhood RedDot consultant that
> > there "might be issues" caused by connecting large numbers of items to
> > a single list. Has anyone done this, experienced problems and would
> > like to share with the group?- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/RedDot-CMS-Users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to