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)
DCT Tabs and Pagination Issue
Tim__D
I tried using tabs on 6.7.1 on Solaris and a few things happened I did not expect.
1 - FormAPI factored in the tab name in all the item addresses. This I dont like still I could work around it.
2 - There is no label child element for tab elements the name displayed to the user is the name of the tab and the name you need to use in your FormAPI. I'd like a label! This way I can have english node names and non-english labels for international use.
3 - Selection list controls on tab #2 were showing through tab #1 when the form finished loading. Not the best user experience. Once clicked the issue seemed to resolve but the initial form is a garbled mess.
4 - The choice popup menu for choice controls seemed to be offset from the clicked + control by the height of the tabs. Again not the best user experience. Removing the tabs removed the offset.
With all these issues I thought I'd try pagination.
I had items-per-page="1" in my data-type node in templating.cfg, one root node and three container nodes. My expectation is that one item per page would render one container per page giving me three pages.
Here is what happened.
First Page After Page Loads
- Last Page Works
- Next Page Works
Second Page
- First Page Fails
- Next Page Fails
- Last Page Works
- Previous page first page buttons broken
- Intiger and return using the form fields works
Third Page
- Same behavior as second page.
Good news is that pagination worked as expected when I removed my FormAPI. I'll look there for the pagination issues but as for the tabs this feature looks like it needs more work.
That being said. I love the way it 'could' work. If anyone has workarounds for the problems above please reply.
Find more posts tagged with
Comments
ccprofessional
I am assuming you are using "xml" type DCTs (tabs only work with xml type).
With "iwov" type, you can have multiple root-containers and pagination works good (although I have seen a minor issue with collapse/expand-all links).
I notice that items-per-page setting is still in the documentation, but it was meant for the old iwov style DCTs before tabs came into the picture.
The tabs feature - i heard from good sources - is also getting some enhancements in 671 sp1. You may want to talk to support about it.
But regarding your issues, try using pagination with "iwov" style.