well, like my title says, I would want the collapsiblock module remember which setting it has on different blocks, for example.

If I set a block to be "hidden" by default, it will always keep this block hidden, even when I have choosed to see it when changing a page, or updating the page.

I imagine that this could be done by using some kind of a cookie?

So what I mean is basically:

"hidden block" stays hidden, until one clicks it, then it shows and when navigating around the page it stays shown until I decide to hide it.
And this should go on until the cookie time runs out (for example 30 minutes or so)

That would be great!

thanks for your work btw!

Comments

nedjo’s picture

Assigned: Unassigned » nedjo

This is a feature that we had in the 4.7 version and dropped temporarily with the 5.0 upgrade. To reintroduce it, we support for the jQuery cookies plugin.

cybertron1’s picture

ok, so it is coming :D

that is great news !

cybertron1’s picture

how is it going with this?? I would like to help, but I don´t know how, not very good at programming, and I would need this feuture quite soon...

what is the problem?? is it possible to go back to the old cookie system while you develop for jquery version??

cybertron1’s picture

not sure if this helps, but he has some nice ideas to use collapsible blocks / content within themes =!??!

http://webschuur.com/node/636

and here is his examples...looks nice :D
http://dev.borchert.cc/drupal/style/themes.html#

cybertron1’s picture

Nedjo: Do you have a timeframe for this ? is it considered low priority? or is it hard to implement? I did try to do it myself, but my coding is far from good, and I didn't quite get it to work (have no idea where to put and change the code) (did find the jqeury cookie plugin, seems easy to use..but like I said, not for me.

nedjo’s picture

Status: Active » Fixed

Added support for cookies through Klaus Hartl's cookie plugin. Applied to HEAD and the 5.0 branch. Not yet in the official release, I'll add it next release (when there are some more features and bugfixes to warrant another release).

Anonymous’s picture

Status: Fixed » Closed (fixed)
psi-borg’s picture

hey i was wondering why this is closed... this feature makes collapsiblock actually usable; if the block state isn't persistent through refreshes, there's no point in having the open/closed option, unless all content is loaded dynamically with no page refresh... not even close to that though are we?

Wolfflow’s picture

Quick chip in:

I was always looking for an alternative approach to this topic. It look like many user would like to have this feature to allow them the inclusion of more informative block but to allow viewer to hide blocks that are of no interest. So far I have used Collapsiblock in D5 but it seems that in D6 a lot of conflict potentiality arise with JQuery, custom JavaScript and so on.

This brought me to search a new way of getting a themable solution, so I have started a topic as: JQuery Collapsible Block with Cookies and it looks promising. With the great help of seutje we worked out a first code strategy.

I have tested this on D6 and it works but some bug are still present. Look at the topic for the last updates.

Regards