block module from 5.8 breaks css and js (reverting to 5.7 block.module fixes problem) [#281026]

On upgrading to D 5.8 I discovered that views_ticker.module is no longer loading its css and javascript.
I have tried moving the commands (which have worked fine in 5.7) to the top of the module but no go.
Everything else is working and the function they are in is pumping out content and it can be seen on the page, but no javascript to drive it. ;-(
The box is Debian 3.1, 32 bit nothing fancy, php 4.3.10-22
drupal_add_js() shows no sign of having been changed in the upgrade, all rather mysterious.
Nothing in php.log or watchdog. All other modules loading javascript are doing so as usual
This issue was originally reported at http://drupal.org/node/280833

If anyone has any ideas.....

Comments

Comment #1

twowheeler commented 11 July 2008 at 00:09

I have been surfing drupal.org, and it looks like anything that depends on javascript is down as of drupal 5.8. Views_slideshow, dhtml_menus, lucid_menus, etc.

Comment #2

kirie commented 11 July 2008 at 03:59

We found this issue too - a CSS file does not load (i.e. not added to the header) after the upgrade. Reverting block.module to the previous version seems to fix the issue - haven't had time yet to figure out which of the changes there causes this.

Applying #7 from #281042: regression in 5.8 from 5.7 theme('blocks','all') broken - so no header alteration possible also seems to fix it.

Comment #3

twowheeler commented 11 July 2008 at 04:54

Thank you! Reverting block.module to 5.7 will do for now, til a real fix is available. Seems to work.

Comment #4

hutch commented 11 July 2008 at 09:30

reverting to block.module 5.7 has fixed it for now, Thanks!
All other javascript is working, at least dhtml_menu and collapsiblock

Comment #5

hutch commented 11 July 2008 at 09:41

Status:

Active

» Fixed

fixed for now

Comment #6

WorldFallz commented 11 July 2008 at 13:22

Title:	css and js not loading for views_ticker module	» block module from 5.8 breaks css and js (reverting to 5.7 block.module fixes problem)
Component:	usability	» block.module
Status:	Fixed	» Postponed (maintainer needs more info)

Reverting a module back to a previous version is not a real fix, just a temporary workaround. Updating issue status and providing a more descriptive title. I'll try to compare the modules and pinpoint exactly where the problem is.