Voting starts in March for the Drupal Association Board election.
I am struggling with the issue that is described here in the CTools queue: http://drupal.org/node/830382
However, it's marked as wontfix there, so I suppose the problem is really with Vote Up/Down.
I use Drupal's built in CSS optimization, which neatly merges the ~40 CSS files used on my site into a single one. However, after updating from Vote Up/Down 1.x, it seems that I'll have to leave it disabled from now on.
When clicking a vote up down widget on a node, several CSS files belonging to installed modules are reloaded separately. These include:
I obtained this list through Firebug. It's not the complete list of course, but that's probably not relevant anyway.
The issue is in the fact that these default CSS files that come with the modules now override my custom styles from my theme, defined in the 'optimized' CSS file.
In other words, clicking the Vote Up/Down widget destroys the entire page layout.
I tried this with all 4 widget types that come with the module, as well as with my own custom widget. The result is the same in each case.
I'm not sure why it's reloading any CSS files at all - I'm sure there's a good reason for it, but it seems to be incompatible with Drupal's built-in CSS optimization.
With CSS optimization disabled, no strange behaviour occurs and everything works as expected. I suppose it's still reloading those files, but because they were already loaded before, the cascading order doesn't change.
I was hoping that there is a workaround for this problem. If there isn't, I will have to leave CSS optimization disabled from now on.
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 0001-Issue-972386-by-merlinofchaos-marvil07-Fixed-Clickin.patch. View