The final tab doesn't appear to work

You appear to have added a font tag on the last tab title which is defining the size & font face of that tab title.

<font size="2" face="verdana">Booking & a few links</font>

If you remove that it should display like the other tabs

Many thanks.

That’s what I thought, but there’s no tags or attributes surrounding it. In fact it’s just the same as all the others because they were copied and pasted and all I did was alter the text. It also seems to be a feature that if I deleted it, the property then transfers to the next one in line. There is a closing font tag ahead of it, so I don’t believe it’s picking up an unclosed tag from somewhere else in the script, but I’m also thinking that’s the only explanation. I’ll go through every tag looking for a corresponding closing tag but I’m sure if there was an open font tag somewhere it would have been picked up elsewhere in the displayed text. It also appears that I can’t have more than 10 tabs (or that’s the most I’ve managed to acheive without it simply refusing to acknowledge the existance of the latest one I introduce). The problem does seem to be confined to the second row. There is a bit of me wondering if there isn’t a theme / plug-in conflict somewhere?

The other thing I should have mentioned, (which must be significant) is that this isn’t necessarily a font issue, but a functionality issue. Clicking on the final tab simply doesn’t return you to anywhere other than an empty white page

The plugin doesn’t add font tags, so you need to find what has caused those to appear.

It is recommended to include a blank line before and after each shortcode to prevent WordPress’s wpautop function from adding unmatched paragraph tags.

All of the html elements in your page between the shortcodes should be nested correctly with each opening tag having a closing tag in the correct place. If you can paste the full text editor content for that page into a pastebin I will have a look to see if I can find any errors in the markup.

Ah ha… found it (I think) half way through the script there is a seemingly erroneous font tag unclosed in a table. I’ve simply deleted this and not only did it restore the font in the tab, it appears to have restored the functionality too. The next question (and I’m optimistic now) is will be allowed to use 12 tabs to break the page into manageable chunks? If I can, then I’ll mark it as resolved and will happily encourage others to use your plug in by way of endorsement, although I have very little money, I ought to make a contribution to this one as I think it’s very good

I think it’s all sorted out now thanks, or at least I’ve got it rigged up and working how I wanted it. Sadly I lack the expertise to tell you precisely what’s happened, so bear with me. So far as I can establish, the tabby tags I’d used were coded correctly. However, there were unclosed font tags elsewhere in the script with some table tags. When tabby met these it broke down. It was probably that it started to display verdana 2 that gave the clue, but it lost it’s functionality. These particular font tags didn’t seem to be serving any function though, so I deleted them, and this restored Tabby. Incidentally, I did encounter a period where some of the bottom of a page remained permanently displayed as if acting as a sticky item underneath the content that the tab was displaying. This has obviously gone now, but it struck me as being quite a good feature. In my case for instance, it could be used to have the forward navigation of the booking process permanently on a page and quite visible without being intrusive and chasing the user around the screen as some of the annoying modern ones do. I don’t know if this is a feature that exists and I’d inadvertantly activated it, or whether I caused it to display some selected content like this, but it actually struck me as being quite good!

There’s no limit on the number of tabs you can have (within reason) and I have successfully used the plugin to display items alphabetically by initial letter with all the items starting with A under the A tab, B under the B tab etc – so I can confirm that a tabgroup containing 26 tabs works perfectly.

If there is something on you site that prevents you from using twelve or more tabs, this is most likely to be caused by a factor outside of the plugin. You may have already fixed this by fixing the other issue, but if not it may have a similar cause which can be fixed by checking for and fixing any invalid markup.