Error! click here!

click on the "Please config the tab title here."
set the title there.
because the block have no tab title by default,
you have to manually set one for the tab

Hi,

i'm using this module on a block displayed on my right sidebar (3 tabs),
it works great but when i'm displaying content using jquery (a really simple external script: on click on an "input type radio ", show a special "div") it doesn't work anymore and i'm getting for each tab "Error! Click here!" and of course no block content displayed... (Tab title are of course well defined :))

Any idea of what's going on ?

thx

"displaying content using jquery"?

you mean you added a block displaying content using jquery?
and embedded within tabbed block?

nope
in the central part, i'm displaying a node content (with template modified) and i'm using jquery to add a simple effect : on click on a input radio button, i'm displaying a hidden div
the tabbed block is on the sidebar on the right with the message "error! click here!"

i also got the same error when i'm displaying node with a simple link with "onclick:print()"

any idea?

thanks.

so there are two errors?
1. a center tabbed block, embedded jquery do not work.? the block is added by "admin/build/block"? the error appears as the modules cannot find a proper title to display.
2. a sided block, with js inside.?

i think the error is not a problem of js.
do other modules(views, user, devel) blocks work correctly within tabbed block?

sorry i'm not speaking english well cause it seems you don't understand me or maybe i don't understand what you're meaning too :)

well, i got a page with 3 columns :

- left sidebar column displaying some blocks,
- center column displaying node content, view etc.
- right sidebar column displaying a tabbed block (3 tabs)

all modules seems to work well (didn't notice any bug)

the tabbed block module works well too except when the center column displays node content on which i'm applying some js (like adding an onclick event on a link) that's why i thought in the first place there was some conflict between the js...

hope you will understand what i'm meaning :)

I'm getting the same thing, all of the sudden...

you mean, orginially it works,
but some how it do not work now?

have you installed a new theme?

Ok, I tracked it down, but I have no idea how to fix it.

I have about fifteen blocks loading in various places on my site. Most of them are controlled with Block Visibility settings, and pull a node object to determine taxonomy or content-type. About 80% of them are views blocks.

What happens is that I added a views block as usual, and then I went to set the block visibility. Immediately afterwards, the (unrelated, unaffiliated) tabs that are views stop working. As soon as I set "Page specific visibility settings" to either:

Show on every page except the listed pages.
Show if the following PHP code returns TRUE (PHP-mode, experts only).

I get the Error! message, on any tabs that pull their data from a view.

Show on only the listed pages. still works, for some odd reason. What's strange is that it happens even if the new block is disabled and has nothing to do with the tabs blocks.

It seems like I've hit some kind of "critical mass" of blocks but I have no idea why or how?? They all still work everywhere else, even the new ones, it's just the pre-existing tabbed blocks that break.

I fixed this by removing lines 302 - 315, the ones that check the block visibility settings for the included modules. I don't need this functionality since I set the block visibility of the actual tabbed block itself - if I want the whole thing included then I want the tabs content included too! But this might not be the best solution for others, I don't know.

Is Version 6 ever going to be finished?????

patched.

Could we get a 5.x-1.4 release to incorporate this?

6.x-1.0 tagged.

"Your official release has been added. A downloadable package will not be available and this release will not be published until the packaging scripts run again. These scripts run every 5 minutes for official releases, so it should be available soon."

so, please wait

Changes at comment #12 makes perfect sense and fixed this issue for me