drupal sets a cookie for each collapsable block. if the number of collapsable block is too high, the maximum number of allowed cookies (50 for firefox 3.x, please refer to http://krijnhoetmer.nl/stuff/javascript/maximum-cookies/ for other browsers) is exceeded, and the older cookie, usually PHPSESSID cookie is automatically deleted by the browser in order to make room for other, new cookies.
how to reproduce:
- use firefox 3
- set up (51 or more) collapsable blocks
I think that the way drupal handles the collapsed/non-collapsed state of the blocks should be changed in order to use less cookies, or only one cookie at all, storing the collapsed/non-collapsed server-side.
sorry for my lame english.
Comments
Comment #1
damien tournoud commentedBy default, Drupal does not manage collapsible blocks. What theme/modules are you using?
Comment #2
kYuZzZz commentedI have the collapsiblock module activated. As the Drupal site with this problem is a production site, I cannot deactive it for now, but I guess that this problem depends on this module being active.
Comment #3
damien tournoud commentedThanks for your answer. Reassigning to the correct project.
Comment #4
nedjoChanged the code to use a single cookie rather than multiple and to set the cookie only for blocks that users have clicked, rather than for all blocks.
Comment #5
kYuZzZz commentedwhich version of drupal has this issue fixed?
Comment #6
nedjoIt's fixed in 6.x.
Comment #7
kYuZzZz commentedis it possible to get a patch to fix this issue for the 5.x version of drupal, please?