• jtlessons

    (@jtlessons)


    Ok, not in a good mood today! First off, I am not a coder and understand basic features & functions of the computer and WP.
    So, when I see a update in my admin panel that says “100% compatible” by it’s author I am going to take it. Because if I don’t my site will not be up to date and could be subject to hacks.
    Recently, a update ruined my blog and stopped a video player from loading. Luckily, I have a competent webmaster who has a functioning version of my site backed up and he was able to “roll back” updates to get the site back to normal.
    WordPress takes NO RESPONSIBLITY for the people who develop plugins and has a smug, carless attitude towards any problem a site owner has by updating a plugin. That attitude is LAME and it needs to change.
    My site is my business card to the world. I am paying for advertising and my webmaster. This is not a blog about food!
    I will be identifying the exact plugins that caused the errors. I would like to feel WP or whoever the [expletive removed] is in a position to hear this type of complaint will do something about it because in fact it is straight up [expletive removed].

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator James Huff

    (@macmanx)

    Hi there, please do calm down a bit. I understand how frustrated you are, but these are community forums staffed by volunteers.

    While every effort is made to stay backwards compatible, there are currently 34,312 plugins in the official directory alone, and there is absolutely no way that the core developers (also all volunteers) can ensure compatibility with all of them.

    This is why the core developers publicly release alpha, beta, and release candidate builds months ahead of the final release, so that the plugin developers can test their 1 or 2 plugins with the upcoming release rather than the volunteer core developers testing the release with 34,312 plugins.

    If a plugin developer chooses not to test their few plugins with the alpha, beta, or release candidate builds months ahead of the final release, there really isn’t much we can do about that. It’s their product and their decision whether or not to test and ensure compatibility.

    Mari-lyn

    (@mari-lyn)

    You can always check the reviews, and if it has been tested with the version of WordPress that you are currently running. This is the best way before you download plugins.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Recent WP Updates Broke Site’ is closed to new replies.