WP Annoyance: False Plugin Compatibility

Before upgrading from WordPress 3.6.1 to 3.7, the Updates page said two plugins also in need of updates were both 100% compatible with 3.6.1 and unknown with 3.7. A conservative administrator might wait for WordPress to list 100% compatibility with 3.7 before upgrading to it. I upgraded anyway because really I use both fairly minimally.

After the upgrade I went to upgrade these plugins and both were listed at 100% compatible with 3.7. Seems unlikely both were fixed in under 2 minutes. So, it seems like even though the data was there for 3.7, for some reason it was obfuscated from 3.6.1? Annoying.

Pick Up Line

(I will never use.)

My name’s Vista. Can I crash at your place tonight?

Noticed at geekpickuplines.

Especially funny for me because the product I run is the Blackboard Learning Management System Vista Enterprise. We just call it “Vista”. (Yes, very confusing when Windows Vista users want to know the compatibility of Vista with Vista. The answer: barely.)

When To Upgrade

After Firefox just upgraded, I noticed it did a check to on the compatibility of the Add-Ons I have. Should any be incompatible, then the add-on gets disabled. The rationale being, “Add-Ons which do not work under the current version should not be enabled.”

Seems like I as the user of the software really ought to have a choice:

  1. (Current) Immediately upgrade the browser and disable any incompatible add-ons.
  2. Check add-on compatibility first and delay the browser upgrade until add-ons are all compatible.
  3. Check add-on compatibility first and prompt the user to choose when to upgrade. (Whether #1 or #2 is desirable.)
  4. Allow the user to choose which add-ons are too important to be disabled and delay the browser upgrade until an add-on version is available which is compatible. Then offer to upgrade both.

Maybe not enough people care Mozilla takes away their functionality?