After repeating the test under several different variations, I have convinced myself that the recent security update knocks out the color selector widget in panels and stylizer. The option to enter the color by hand is still available, so it is not a major hurdle, but the down time required to isolate things like this is really adding up. So many modules are routinely updated that I finally realize the foolishness of updating them as they are released. A single update can knock out a feature and you don't find out for weeks or months. Trying to isolate newly introduced bugs becomes way too time intensive for me. Especially in this sea of constantly changing code. I think, with the obvious exception of security issues, if it does what I want it to do, then I'll just leave it alone. I guess that is probably common knowledge, though. Just a little survival strategy to work out.

CommentFileSizeAuthor
#4 1510428-fix-stylizer-add.patch569 bytesmerlinofchaos
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

merlinofchaos’s picture

While I understand that you are frustrated about changes made from updates, you have entered a bug report with two half sentences about the actual bug and then another 5 sentences about the update process.

It makes it difficult for those of us interested in fixing the bug to separate the important information from the less important information. Now, I really do understand, I hate it when I produce updates that add new bugs at the same time as fixing old bugs. Unfortunately, this is one of the hassles of open source. Also, the issue queue is not really the forum. I understand, though, the need to vent your frustrations. Please also understand that I work very hard on this software, and such venting can be very demotivating to module maintainers.

On the plus side I was able to reproduce this pretty trivially and I see a javascript error that should make this easy to fix.

robatk’s picture

Your points are well taken. Thank you for being understanding about my need to vent. Also, your courtesy speaks well for your professionalism.

merlinofchaos’s picture

It appears that reverting this patch fixes the problem: http://drupalcode.org/project/ctools.git/blobdiff_plain/4eb1e2f0882387a9...

Are you able to apply patches? That will get this fixed for you right away. We need to figure out the proper way to add the farbtastic library to fix this the right way but that will get you going.

merlinofchaos’s picture

Status: Active » Fixed
FileSize
569 bytes

Ok, the drupal_add_library call had the wrong name for farbtastic. Attached pack fixes this and is already committed and pushed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.