Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Mike Jolley (a11n)

    (@mikejolley)

    Hi, the plugin has worked for lots of people 🙂 You need to run the data upgrader for your images to come back. There is a huge notice after upgrading which you must have missed.

    I’d suggest a notice be shown prior to the upgrade so folks don’t get the surprise after commitment. I didn’t see anything about a db upgrade or effecting images when I read the notes prior to upgrading, really glad I used a staging site.

    side rant…
    IMO, there should be a way to upgrade themes and plugins without down time. WordPress is very poor in this area.

    Why can’t two versions of a plugin coexist and WP be smart enough to know which is active? It seems pretty simple logic to me, if v1.0 is active and one uploads v1.1 and activates it, v1.0 becomes disabled. Easy upgrades, easy roll backs. I realize this is not the forum for this suggestion but it is related to the general feeling of the community as it relates to updates. Shiny updates are great but why destroy the previous version when we can be smarter about our approach?

    Caleb Burks

    (@icaleb)

    Automattic Happiness Engineer

    This is what staging is for, no?

    @caleb Burks Yes indeed but if measures were in place to allow non-destructive upgrades and rollbacks, it’d be less necessary for routine maintenance.

    Been trying out versionpress for about a month. It’s nice if you have the resources to run it.

    Caleb Burks

    (@icaleb)

    Automattic Happiness Engineer

    Versioning like that is probably never going to be handled by WordPress core though. Versioning can take place in many different places, such as SVN / Github or an extension like VaultPress or VersionPress.

    Having WordPress handle plugin versioning while also running versioning on your own somewhere else would be a mess. Also could cause security concerns.

    You could be right and that really wasn’t what I was suggesting. Just pointing out there are tools that recognize that WordPress has a very risky and destructive approach to upgrades requiring outside solutions to alleviate the risk or hassle otherwise. A non-destructive approach to upgrades within the core is still something very much desirable and I know I’m not alone on this.

    Plugin Author Mike Jolley (a11n)

    (@mikejolley)

    It’s a problem all plugins will run across, but without WP core support there isn’t really a viable solution.

    I did see versionpress and it looked good. Vaultpress (rollback support) is also good if you’re non technical, but nothing replaces a staging site.

    Yes and there are even some solutions popping up that bring staging into the wp back end as a plugin solution which is pretty neat but also on the fringe side of things too, where most only really work if your server environment supports it. For now wp cli to the rescue but again that’s if the server allows it.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Problem with version 2.6.1’ is closed to new replies.