marsili.us

You said, “It’s not a Supercache problem unfortunately. It’s a WordPress problem that was introduced in 3.3.” As an Oracle developer, I sometimes encountered cases in which a change in the Oracle RDBMS software “broke” one of my procedures or scripts. Oracle software upgrades were infrequent and, in any case, I judged I couldn’t control whether Oracle, Inc., would eventually make a change that would restore the operation of my broken procedure. So I just made little adjustments in my own code that would restore the procedure to usability in the new circumstances.

I don’t know whether this case involving WP SuperCache and WordPress 3.3 is sufficiently similar to warrant comparison. Maybe in this case, there seems to be simply nothing you can do, or maybe there seems to be nothing you can do in the time you have available. Also, I do keep in mind that WP SuperCache is “free ice cream” and that past benefits don’t entitle us to future benefits. However, if you can reasonably make some change in WP SuperCache 1.0 that will allow it to work with WordPress 3.3, those of us who have faced similar problems in our own work as developers will be able to appreciate that your finding and implementing a solution doesn’t imply your having been to blame for the problem in the first place. And we and the rest will be grateful for your continuing help.