• I have downgraded back to 3.1.4. I doubt I’ll be updating again to 3.2 for a month or two while premium develops catch up and I update several custom solutions. (I’m serious about a month or two, at minimum. Some premium shops are one-man or small team outfits with several dozen plugins and themes that need to be updated to match 3.2. Those changes aren’t coming overnight.)

    I *do* appreciate the hard work put into WordPress. I don’t appreciate being swamped by dozens of clients because a .X release breaks dozens of plugins (that I’ve encountered *so far*) and seemingly most JavaScript heavy themes.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Thought Police

    (@tpifiction)

    Bah, hit the post button before I was done (the hazards of pets).

    My request is some clear guidance on coding updates. Saying that X or Y version is required or that JQuery is updated to whatever (actual types of answers I’ve seen here) is not clear guidance. I mean what deprecated commands are most likely to be culprits? With JavaScript breakage causing alignment, scroll functionality, and similar issues, what is the most likely cause and best solution? That is the sort of feedback and advice I’m looking for.

    If we’re going to get a functionality breaking version of WordPress, we should at least get some details on how to going about repairing the problems.

    Thread Starter Thought Police

    (@tpifiction)

    Rereading my message, I apologize for any rudeness. I am just very swamped and frustrated. My post reflects that, but it’s no excuse be a “donkey”. So again, I apologize. I certainly could have conveyed my frustration in a much more polite fashion. I understand you’re volunteers and I really do appreciate all the work that goes into this wonderful software.

    Also, being clearer about the problems, plugins typically throw off a variety JavaScript errors or cause a WSOD while themes typically run into major display issues (misalignment, missing images, broken scrolling, etc).

    In a perfect world I totally agree with you.

    In a world of where you can write a function in 100 different ways, where there are over 10 000 of plugins and themes there might be a glitch here and there, the best thing you can do right now, is to share your problem(s) and we can all help solve them for you, and maybe someone else have the same problems.

    But yes i can understand your frustration, when a new version of WordPress comes with all it’s awesomeness you want it right away and everything to work.

    I don’t know if this help, but I did sign up for the developers newsletter, I won’t promise you find all the information here, but sometimes there are some good insights. (of what you where asking for)

    sorry for my poor english, its not my native language ??

    Edit: this one is quite good also, https://www.ads-software.com/support/topic/troubleshooting-wordpress-32-master-list?replies=7

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WP 3.2 destroys swaths of themes and plugins’ is closed to new replies.