Fivestar with problems with HTMLBox Module
Rosamunda - November 11, 2008 - 02:51
| Project: | HTMLBox |
| Version: | 6.x-1.0-beta5 |
| Component: | Code |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | active |
Description
Fivestar was working perfectly ok, until I´ve updated Drupal to 6.6 version.
I´ve unchecked all contrib modules (except fivestar), and it doesn´t seem to work either.
Some of the errors that appears are these:
The arror appeared on: /admin/settings/fivestar
Error Message: Parsed JavaScript file sites/all/modules/fivestar/js/fivestar.js.
When I try to enter the settings page, the color picker isn´t there. And I simply cannot check the availability of fivestar to any content type (it appears in grey).
Don´t know whay is doing this. I´ve updated to the latest fivestar version, end even t the dev version. But it just won´t work.
Thanks for your help!!
Rosamunda
#1
Sounds like you might be having an error with the JavaScript compressor. Try visiting admin/settings/performance and turning off the javascript compressor (first), then try turning off the aggregation next. If it works after that, you might also try clearing all your caches by clicking the "Clear all caches" button at the bottom of the performance page. It might be that something in the 6.6 release is breaking compression, though it seems to have worked fine in all previous versions.
#2
Thanks for your reply!!
I´ve done everything you´ve said. But the problem is still there.
I´ve attached an image that shows the problem.
As you can see there isn´t anything more in the settings page, so the color picker isn´t there...
#3
Nobody has this error with 6.6 version??
#4
After struggling a lot, I think I´ve discovered the incompatibility: It seems to be with HLML Box. I must confess that I´m not quite sure, because I´ve disabeled some other modules too: Conditions, Live and Contact Link.
But as HTML Box had provoked me other issues, it´s my guess that he´s the, erm... primary suspect.
I´ve marked this as fixed because I don´t think it´s a "fivestar bug" after all :)
Thanks!
#5
Thanks Rosamunda for following up on this issue.
#6
Automatically closed -- issue fixed for two weeks with no activity.
#7
i can confirm this bug... deactivating HTML Box solves the problem...
#8
Let's move into the HTMLBox queue, as it's likely a problem caused by it.
#9
I may add (now that we´re in the HTMLBox queue ;) that this module doesn´t work as expected, at all.