Closed (fixed)
Project:
Quick Tabs
Version:
5.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Mar 2008 at 03:22 UTC
Updated:
8 Apr 2008 at 19:12 UTC
Many thanks for this module, it works a treat and so much quicker to create tabs.
However, i think there is a minor error. One of the tabs i've added isn't showing up the block name in the CSS. This is what i get looking at the source code of my site:
<div class="quicktabs"><div class="block block-" id="block--">
That is what i get for my recent posts and comments tabs, see: www.duvien.com
The tabs still works fine but it's not valid CSS because of the id="block--"
How can this be resolved? how would it be possible to remove the 'id= ' as it is not needed anyway.
thank you,
Comments
Comment #1
katbailey commentedHi Duvien,
just to update you on this: I have fixed the issue and it is important enough to create a new release for it. But unfortunately the drupal.org packaging script seems to be having problems so my new release can't get published yet. I will update again when this issue has been resolved.
Thanks for the bug report - good catch!
And by the way I really like your site and it's great to see quicktabs on there! :-)
Katherine
Comment #2
onejam commentedThanks for the compliment. However, without quicktabs or the community help. I don't think my site would have existed.
I'm sure i'll give back, perhaps a free drupal template (using the grid layout) and some tutorials. :)
Comment #3
onejam commentedHi Katherine,
I know you are busy but any joy with fixing the drupal.org packaging script? If not, would it be possible to post up a patch file so i can test it out.
Thank you,
Comment #4
katbailey commentedHi Duvien,
it's up there now - I had provided a link to the tarball anyway but now it's being listed properly so please go ahead and download and test it out and confirm that it's working properly.
Thanks!
Katherine
Comment #5
onejam commentedKatherine, many thanks for your excellent work.
I can confirm that it is now resolved. :)
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.