quicktabs only work in admin mode (when block cache is enabled)

possible problems:

1. disable block caching on admin/settings/performance page
2. check the visibility settings at admin/build/blocks > configure

exit to a regular view

is that mean logging out, or (you use a different site and administration theme and) you just changing the theme?

it seems like nor css nor js files are added to the page when this situation happens.. I have no idea, how could this happen.
If the quicktabs are rendered as any other block, then the files should be added to the page.
If you know firebug, then you could check the required files: quicktabs.js, quicktabs.css, quicktabs-stylename.css

If the quicktabs are not placed in a simple block then that could be a problem. could be a similar issue: #343016: Node blocks aren't working in ajax

then, it is definitely the problem with your browser. you probably need to clear the browser's cache (and the cookies maybe)..

there is no delay, the changes are applied immediately when the save button is clicked..

I have just started using quicktabs and realized that I am seeing the same problem as the original poster, reinartj.

1: logged in a user1 I see tabs
2: logged out, no tabs and
3. bulleted list of tab names are linked to completely unrelated nodes! (all the same for each tab block)

Clearing the site cache made the random links go away, but still no tabs when logged out.

1. do you have block caching enabled on admin/settings/performance?
2. which browser do you use? please try it in a different browser(s).
3. try enabling the "Optimize CSS files" option on admin/settings/performance page

Hi, Thanks -

1. I have block caching enabled now, but it was off when I started using quicktabs.
2. I/m using Safari and tried it in Firefox - the results were the same. I cleared the browser cache, then the site cache, and tried another browser.
3. I'll try "Optimize CSS files" but my experience has been that this makes the page load even slower than it is now and any slower would be not too good. But I will try it.

------
Ok, I've tried your suggestions and quicktabs are now showing up when logged out, but the pages load slower than ever with the optimized css. Does that have to stay on for qt to work? I'll put the qt blocks back where they should be and leave them to test a while. If you can, look at the site and let me know if they look ok to you. http://www.fromoutoftheblue.com

Thanks again.

=================

But then I tried it in camino and only tab 1 would display. I'm giving up on it because this has taken a lot of time already and it is still not stable enough to leave alone.

From the answers I would tell the problem is with the enabled block caching. QT does not work correctly if block caching is enabled. There are already some issue about it in the issue queue..

The new version seems to be working. Except, in one block, with FireFox, one tab displayed the wrong item. I checked everything and the other browsers displayed everything correctly. FireFox has terrible caching anyway.

Thanks for the new release. I was going to say that another module, tagadelic, had caching problems immediately following a drupal core update. A patch was written and it worked, then a new release was issued and the caching problems went away.

Thanks to all the module makers.

I do not know about any change between -rc1 and -rc2 which would possibly fix this problem. So I am still thinking that clearing the Drupal cache (at update) made it look like, that it works..

if you still have block caching enabled, then you should try:
1. admin/settings/performance disable the block cache
2. admin/settings/performance clear cached data
3. go to that page where the quicktab block is wrong
4. hit refresh in the browser

I have nothing to add to this issue and all questioners seems to be satisfied..

You are right, Pasqualle - Quicktabs does not work. I see now that only the first tab will show up and that qt appeared to work was probably due to the clearing of the cache after updating.

I don't know your actual setting for block cache (in your last post you said it is on). The block cache is most probably the issue here.

you need to disable the block caching, or you can try the latest -dev release (where it is automatically disabled for QT blocks)
see: #342459: Block cache problem (Not showing for anonymous or authenticated users)

Block cache is disabled. Has been.

I will try the latest dev.

Thanks.

=============

I just tried dev-Jan 22. Same problem, only one tab shows when logged out in Safari. This was after clearing cache again. In FF, after all caches were cleared, QTabs worked, but it may be temporary, as it was last time - but Safari did not pass after FF.

I have checked your site. Those quicktabs are pretty well broken and I have no other explanation than this must be a caching issue..

you are using a non-ajax quicktab. the normal html structure for a non-ajax quicktab with 3 tabs is:

quicktabs-1
-quicktabs_tabs
--qtab-0
--qtab-1
--qtab-2
-quicktabs_container_1
--quicktabs_tabpage_1_0
--quicktabs_tabpage_1_1
--quicktabs_tabpage_1_2

the last 2 tabpages are missing completely on your site. If the non-ajax quicktab is rendered at page load, then all 3 tabpages must be there. Here is the corresponding code (from quicktab.module)

  if (!$quicktabs['ajax'] and _quicktabs_javascript_enabled()) {
    // Render all tabpgages.
    foreach ($quicktabs['tabs'] as $key => $tab) {
      $attributes = drupal_attributes(array(
        'id' => 'quicktabs_tabpage_'. $quicktabs['qtid'] .'_'. $key,
        'class' => 'quicktabs_tabpage',
      ));
      $output .= '<div'. $attributes .'>'. quicktabs_render_tabpage($tab) .'</div>';
    }
  }

only solution I see:
admin/settings/performance clear cached data, and check again..

can you give me the result of this SQL statement?

SELECT ajax FROM quicktabs WHERE qtid = 1;

can you list the modules used on the site?

I am interested in special javascript or cookie handling modules..

Hello Pasqualle, I just tried the latest dev (1/23) and checked QT in Camino (which is not the default browser) and it looked ok. I checked in Camino so browser caching would not be an issue.

If you still want a list of modules, I'll be back later to do that for you. I have quite a few actually.

Thanks.

@2createwdrupal: it does not work on the front page only. when you try the quicktab block on other pages it seems to work correctly.

are you using any special module like boost or similar? if you could give me the full list of modules what you use that would be the best..

@Pasqualle - I made a series of screenshots for you of all the modules I have installed. You'll see that not all of them are enabled and of those that are enabled, several I am not actually using. (There is one that does not go away even though I've removed it from the server.) Also, there is one other jQuery script, interfade, that is in use.

Hope this helps. Let me know what you find. Thanks.

I don't see any cache or front page related module.. Will test some to try to reproduce the problem or try to find a possible conflict.

I don't have a separate front page. The only difference is that the theme displays the "mission" box on the front page.

Cache module?

I just installed your latest dev. Tried in Camino, seemed ok after an extra of refresh. I used Camino to test because it doesn't have caching issues. FF might display a 4 day old page even though I have caching disabled in it.

@2createwdrupal: your problem is a duplicate of #363145: Missing tabpages in non-ajax mode

The original problem in this issue seems to be different and fixed.

Hi Pasqualle,

Thanks for keeping up with all this.

I just tried the Jan31 issue of QT and I saw that quicktabs immediately worked in Camino. Then I tried FireFox and QT did not work. But then, FF has a lot of caching problems so maybe it is working somewhere in the world where FF is used. What do you think?

Peter

I just tried the Jan31 issue of QT

I don't understand what you tried. I don't see a new -dev release yet. Did you downloaded QT from the CVS or manually patched QT with the latest changes? Otherwise you don't have the fix..

there was a dev release dated Jan31, then Feb1. I now have the one dated Feb1 installed.

Today, using the new Safari 4 beta, Quicktabs did not work until I logged in as admin. Sorry to have to bring this news in again.

if you enable block caching
(with or without css and javascript compression - does not matter)
the quicktabs seems broken for all users except the admin which sees everything normal

its like the javascript never gets called to create the tabs

as soon as block caching is disabled everything is back to normal again

@GiorgosK: if you have a block cache issue, then please follow the issue #342459: Block cache problem (Not showing for anonymous or authenticated users)
It should work correctly if your {block} table 'cache' column contains -1..

@Pasqualle

thanks the change of cache -1 did indeed fix this issue