I’m going to guess that the vast majority of you who find this post probably won’t even have been affected by the horrible NIGHTMARE of a release yesterday, as I reverted the stable tag back to v220.127.116.11 very quickly after receiving tons of reports about fatal errors upon upgrading. However, for those of you who did… This release is for you!
Those of you who did not get a chance to download v3.0 should consider yourselves lucky, as I seemed to have “jumped the gun” a bit and released it before I tested thoroughly. At any rate, v3.0.1 addresses each of the issues that arose in v3.0 and also adds a couple small finishing touches as well.
Considering the level of mayhem associated with the v3.0 release, I would say that the biggest lesson I’ve learned from it would simply be this:
QUIT USING THE HOME ROW TO CODE!
The reason so many of you got fatal errors when upgrading was because my pinky finger apparently pressed the semicolon key inadvertently while coding. May not sound too terrible if you’re not a coder, but trust me… PHP didn’t like it one bit! Anyway, here’s a list of what was fixed/added in this release:
Fix for fatal error upon upgrading to v3.0
Fix for Google Bookmarks image not displaying correctly
Fix for spritegen not working if wordpress installed in subdirectory
Spritegen now outputs minified CSS as well
Added activation hook to generate sprite automatically upon activating the plugin
Don’t forget v3.0 features!
Since most of you will be upgrading to v3.0.1 directly from v18.104.22.168, you may want to go see what features were added in v3.0 as well!
There are currently 4 primary types of bugs being tracked with this release:
- Upon installing/upgrading, all icons disappear and are replaced by text links
- Upon installing/upgrading, a list of “Uncaught exception” errors is displayed
- Upon installing/upgrading, a list of “filesize()” errors are displayed
- Upon installing/upgrading, “Invalid argument supplied” errors are displayed
Please be patient as we are working frantically to find the common link between each of the errors so that we can get it fixed as soon as possible. I guess it’s a bit ironic that this was a “bug patch” release, and yet it’s still apparently full of bugs, eh?