SOLVED: Tabbed Content Pages
Posted: Tue Apr 10, 2012 3:03 pm
Hi all 
OK I have a question regarding tabbed pages which I cannot find the answer to anywhere else on the forum (or online!).
My product pages on my website are made up of a summary area and then a number of tabbed areas. For example:
http://www.videocentric.co.uk/video-con ... cius.shtml
I have 2 scenarios created:
1. When the website was ported across to CMSMS, a "summary" template was created for us which would then take any children pages and create these as tabs. This is great due to the fact each page can have a different number of tabs/different names etc.
My problem with this is that for every page I want to create, I have to create around 5-6 pages, without being able to jump between each from one another, it is very time consuming and each tab then shows as a different page in my website search function (but without formatting which creates a huge confusion).
I used the <-- pageattribute: notsearchable --> in the template for the children pages to try resolve the search problem but the pages still show in the search.
2. I have just created a new template to make this much quicker to do - I have used a number of content blocks - but by doing this I am now restricting myself to the specific tab names I have set in my template, and then certain number of tabs I can have.
Questions:
1) For the first example, does anyone know why the notsearchable code didn't work?
2) Is there a way to create a template as in 2. but with the ability to specify each tab seperately (i.e. have a summary content block and then a dropdown/text box to specify how many tabs required, and then the right number of title and content blocks "appear"?
3) I know 2 sounds a bit far fetched, but in an ideal world this is what I would like... any other ideas would be most appreciated!
I look forward to hearing you comments or any ideas. I am quite a newbie at all of this stuff so please be nice
Emily
(please excuse any webdev/coding mess - it was ported across last year from an old dreamweaver/table format and has not been fixed yet due to time/lack of understanding...)

OK I have a question regarding tabbed pages which I cannot find the answer to anywhere else on the forum (or online!).
My product pages on my website are made up of a summary area and then a number of tabbed areas. For example:
http://www.videocentric.co.uk/video-con ... cius.shtml
I have 2 scenarios created:
1. When the website was ported across to CMSMS, a "summary" template was created for us which would then take any children pages and create these as tabs. This is great due to the fact each page can have a different number of tabs/different names etc.
My problem with this is that for every page I want to create, I have to create around 5-6 pages, without being able to jump between each from one another, it is very time consuming and each tab then shows as a different page in my website search function (but without formatting which creates a huge confusion).
I used the <-- pageattribute: notsearchable --> in the template for the children pages to try resolve the search problem but the pages still show in the search.
2. I have just created a new template to make this much quicker to do - I have used a number of content blocks - but by doing this I am now restricting myself to the specific tab names I have set in my template, and then certain number of tabs I can have.
Questions:
1) For the first example, does anyone know why the notsearchable code didn't work?
2) Is there a way to create a template as in 2. but with the ability to specify each tab seperately (i.e. have a summary content block and then a dropdown/text box to specify how many tabs required, and then the right number of title and content blocks "appear"?
3) I know 2 sounds a bit far fetched, but in an ideal world this is what I would like... any other ideas would be most appreciated!
I look forward to hearing you comments or any ideas. I am quite a newbie at all of this stuff so please be nice

Emily

(please excuse any webdev/coding mess - it was ported across last year from an old dreamweaver/table format and has not been fixed yet due to time/lack of understanding...)