In particular, Aquasoft, but I've seen problems in others as well.
For example, Collapsable blocks don't work. In my debugging, I've found that the jstools code relies on certain standard structure and naming practices be followed for it to have the desired effects. While many newer themes follow these, some do not.
In particular, for collapsable blocks, the block must be enclosed in a div tag with a class type of block. Inside it, there must be another div tag with a class name of content. And if that is not enough, the heading text for the block must be in an h2 tag. Aquasoft follows none of these conventions.
So I'm not sure if this is a bug in Aquasoft or in jstools or if there is a need for a well designed set of rules for themes in Drupal that needs to be better communicated.
In the interrim, perhaps jstools can be generalized through settings to handle the various cases. Or perhaps jstools can propose some standard way that enables a theme to inform jstools about the tags and structure the theme will emit.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | cc_screen_bug.png | 206.29 KB | liza |
Comments
Comment #1
krzysiek@palikowski.vel.pl commentedI confirm that collapsible blocks and active menu can mess with collapsible panels in drupal - they worked for some time and suddenly stopped to work for some time... after i cleaned cache and logged off/on - it works again :) ... strange?
Comment #2
liza commentedSame here.
I am using a customized theme based on Marvin2k PhpTemplate. The theme and collapsiblocks work fine in Firefox and Safari. For some bizarre reason, not only do the blocks don't collapse in IE, but the top three boxes on the far-left sidebar disappear.
Comment #3
joel_guesclin commentedI'm trying to get this to work on 4.7.4 using standard Bluemarine theme. The block definition seems to correspond to what is said in above, eg:
The blocks appear on screen but no sign of them being collapsible. I am working in Firefox and the js version is:
The only thing I can add is that the js console shows the following two errors:
and this
It all seems a bit shaky at the moment - how safe is it to suppose that these things will work in users' browsers?
Comment #4
nedjoDo you have the jstools.module enabled? That's what defines the jsTools object.
Comment #5
joel_guesclin commentedOk, that sorted it for me - thanks for the tip