Let me tell you something, there is nothing more prone to getting me anxious than noticing or being notified of an error on a CommentLuv release when I’m at work and it’s busy. NOTHING!

Shear panic sets in,

  • “what about all the people who just downloaded it?”
  • “oh dear, I have to send out ANOTHER email to the members, how many sweary replies will I get from people that can’t find the unsubscribe link that’s just below the bit that says “unsubscribe here”?”
  • “what new language will I have to learn to overcome this problem?”

Instant research, google refusing to display. FTP details lost again. customers constantly ringing in orders.

take a moment. feel acid build in belly.

read the error and use Yahoo (pah!) to search for an answer.

Minutes later, realize that it’s a WordPress bug… “phew!, not my code!” .. moments later … “oh shit, how will I fix this then?” .. hours of messing up peoples change and forgetting to save an order while thinking about all the above..

.. minutes after rushing the close-up at work … “I’ll just rewrite the htmlspecialchars_decode function and use that instead” ..

head.scratches
expletives.shouted

Solution tested on php4 blog. Works. Send out a couple to those who are experiencing the error.

wait with baited breath for them to reply that it works before I can update the repository.

they do! in email and on twitter. good on ya @mitch_m!

CommentLuv v2.7.61 gets uploaded to the repository.

wait with trembling trembles to see if the jamungous amount of people that have to update again will do it and not get in a fuss and disable it instead.

oh gosh. writing software for free is fun! :-)