Tabs and form API

Hi,

Do we need to add the tab name when accessing dct fields in Form API? and also if there is a space in tab name (example: Tab 1), will there be any issues with Form API?

Find more posts tagged with

Comments

Adam Stoller

Hi,

Do we need to add the tab name when accessing dct fields in Form API? and also if there is a space in tab name (example: Tab 1), will there be any issues with Form API?

To the best of my knowledge, FormAPI does not across / between tabs at all, and I'm not sure it works all that well within a single tab on a tabbed DCT (you might have to create separate script instances within each tab)

So, in general, while tabs might present a reasonable interface for some things, they tend to present problems for making the interface nice for other things.

Unfortunately, I don't believe the documentation says this anywhere

RajatChopra

We are evaluating tabs as well at present.

How does the XPATH of the tabbed pages differ from a regular one? I guess it should behave in a manner similar to a container. So you should be able to access the items by adding the tab name to the XPATH while accessing those items.

I haven't tried this myself, will have to start soon. Can someone who has used this already post their experience with tab pages, form API, meta-tags, etc.

Thanks,
Rajat

getnaren

Rajat,

Tab name should be used in the xpath, and it works fine, but the tab name cant have space like this

"Tab 1" it can be "Tab1"

We are evaluating tabs as well at present.

How does the XPATH of the tabbed pages differ from a regular one? I guess it should behave in a manner similar to a container. So you should be able to access the items by adding the tab name to the XPATH while accessing those items.

I haven't tried this myself, will have to start soon. Can someone who has used this already post their experience with tab pages, form API, meta-tags, etc.

Thanks,
Rajat