Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Paging of DCTs
pawlr
Is it possible to configure TS interface so that for really long lists of replicants, you can page the form, so that it doesn't try to load 100-200 elements into the page (takes like 2 minutes to load each time you move an element). Or if anyone has some better suggestion for how to structure my data.. its for a list (I would use a database if I could but I'm limited to flat files)
Find more posts tagged with
Comments
Adam Stoller
I think the paging aspect of DCT/DCRs is limited to top-level items - of which the 'replicant' is one, so the number of sub-elements in the replicant aren't considered in that respect.
Does it make sense for all these items to be in one DCR?
Does it make sense for all these items to be in one replicant?
Only you can really answer those questions, as it's a matter of your processes and procedures and what you're doing with the data that determines whether or not you can break them up in other ways.
Other than filing a feature request and/or trying to code your own Edit DCR UI, I'm not sure there is too much you can do - it's kind of a classic problem with forms (as opposed to text-based content which can more easily be paginated)
--fish
(Interwoven Senior Technical Consultant)
pawlr
Thanks for your response.. I thought about it and realized that no, they didn't all need to be in one dcr, as long as the .tpl could load all the dcrs via perl and output all the replicant items in one file.. I remember seeing this in a previous post but couldn't find it, if you can point me where, I'd appreciate it.. thanks again
Adam Stoller
Before you go down the road of muyltiple DCRs - consider that if you're willing to put items in separate DCRs you could put them on separate pages in one DCR (i.e. set a small number [1, maybe 2] for items-per-page in the DCR). If that's too much of an extreme in the other direction, then consider looking at breaking up the DCR.
As for pointers, I'd be looking at the manuals and searching through these forums for a start - and at this point it would probably be better if you do that than have me do it for you.
--fish
(Interwoven Senior Technical Consultant)
pawlr
Fish--thanks, but unfortunately since I'm dealing with a really large replicant (200 items), "items-per-page" won't work, according to your earlier post..
http://devnet.interwoven.com/forums/cgi-bin/showthreaded.pl?Cat=&Board=PRODUCTS_TEMPLATING&Number=7028&page=&view=&sb=&o=&vc=1#Post7028
Actually I already went down the mulitple-dcr approach and I got it to work using 3 nested foreach statements in perl..
thanks anyhoo--