Anyone in Technology for a while has seen arrogance by various companies who think they are the kings of their market. Among the saddest stories include the makers of Quark and the Lotus Office Suite. Oh wait, what? You never heard of them? Then you must be under 30.
Recently Adobe took a buttload of crap when they refused to support a 64 bit version of the Master Suite for their Apple computer and then there is the never-ever ending of Microsoft and their browser… what was that? Internet Exploder?
This week a product that I have personally taken to fall in love with, especially for clients who need easy back-end access to their sites, is the almighty WordPress. Unfortunately, WordPress went on a diet and forgot to tell anyone with the release of WordPress 3.2.
Like in most cases I updated about 4 of my sites, including this one, and was suddenly locked out out a lot of the controls used to manage the site. Did you visit in the last few days and see something far less brilliant than what you see now? Well, I had the kind folks at my hosting company www.HostHead.com restoring my site to pre-3.2!
WordPress says with their release of 3.2.1″
“After more than a million downloads of WordPress 3.2, we’re now releasing WordPress 3.2.1 into the wild. This maintenance release fixes a server incompatibility related to JSON that’s unfortunately affected some of you, as well as a few other fixes in the new dashboard design and the Twenty Eleven theme. If you’ve already updated to 3.2, then this update will be even faster than usual, thanks to the new feature in 3.2 that only updates files that have been changed, rather than replacing all the files in your installation.” – Source
In the above WordPress blog there is not even an apology. With the barest of acknowledgements to major major changes I have to wonder how much of those ‘million downloads’ resulted in jacked up web sites.
When I posted for help in the Support Forum indignant and rude people who identified themselves as volunteers wrote comments to other posters that were just uncalled for and just plain bitchy!
I still have other sites needing fixing. WordPress ‘volunteers’ basically told me I had to rebuild my sites in order to recover them. While I was lucky to restore a back-up on StudioSK, one of my sites is a very busy social networking site that my hands are tied with and will have to be done at some odd hour once I finally figure out my approach.
Other designers and developers have reacted with curiosity through my Twitter (@scott4design) because not all experienced this horrible result like I did. What got some people through an easy upgrade and so many others with a fumble with a face-plant is beyond me.
The biggest problems I experienced were:
- widgets would not open to allow for editing
- menu’s for images libraries would not open
If there were more then I did not discover them yet. On my social networking site www.gayburners.com members are having trouble logging in and posting images, setting up groups and what else? What am I not hearing about?
This update with WordPress 3.2 may have been created to be more efficient and break away from some old baggage with IE6 and more, but at what price? How come your users were not given some warning? This upgrade should have had a lot more warnings and acknowledgements, because I know I would have appreciated it.
WordPress is the best CMS on the market in my humble opinion. It is the one you can give any client and let them go with it. But if I left this update to a client alone… they would have had no where to go.