WP Rollback compatibility

  • Hi, since last updates I encounter some issues while managing plugins activations. When activation Error log monitor (ELM) other plugins are disabled and vise versa. Rolling back to 1.6.6 (didn’t test 1.6.7) seemed to solve the issue for now. So what happened in between ?

    For such purposes can you please keep your previous versions in the WP directory to make it compatible with “WP rollback” plugin, or do whats needed for it.

    > Here is a notice from another plugin that faces issues to help you in the process :

    It appears there are no version to select. This is likely due to the plugin author not using tags for their versions and only committing new releases to the repository trunk.

    Regards.

    • This topic was modified 5 years, 3 months ago by tdechangy.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Janis Elsts

    (@whiteshadow)

    The previous versions are already in the www.remarpro.com directory. See the Previous Versions section in “Advanced View”. I’m not sure how WP Rollback works, but if it gets old versions from this site then it should be able to retrieve those versions.

    When activation Error log monitor (ELM) other plugins are disabled and vise versa. Rolling back to 1.6.6 (didn’t test 1.6.7) seemed to solve the issue for now. So what happened in between ?

    Versions 1.6.7 to 1.6.9 only contained small bug fixes and Freemius SDK updates. Freemius SDK has had some issues in the past (especially on Multisite), but so far nobody has reported other plugins being disabled. Also, I use ELM 1.6.9 on a couple of my own sites and I haven’t noticed any issues with plugin management.

    To help figure out what’s going on, could you please answer a few questions?

    • Is this problem happening on a regular site or a Multisite network?
    • Is there anything unusual about the plugins being used on that site, like multiple versions of the same plugin being installed at the same time?
    • Is the database working fine? The list of active plugins is stored in the database, so in rare cases a database problem could make WP deactivate all plugins or prevent you from (de-)activating plugins.
    • Are you using a DB caching plugin? Similar to the above, a caching glitch could interfere with plugin activation.
    Thread Starter tdechangy

    (@tdechangy)

    All right thx, I assume there is an issue with DB or Caching (WP fastest Cache). But I don’t have PHP dev skills and we don’t have financial resources for this site now to engage a developer for it… I’ll make some tests to figure out what’s happening.

    By the way could you eventually make the compatibility clever with WP rollback as mentioned :

    It appears there are no version to select. This is likely due to the plugin author not using tags for their versions and only committing new releases to the repository trunk.

    I’ll use your suggestion until that :

    See the Previous Versions section in “Advanced View”.

    Regards.

    Plugin Author Janis Elsts

    (@whiteshadow)

    It’s odd that WP Rollback would show that message given that I am in fact using tags for ELM versions. You can see the tags here. I’m not sure why WP Rollback isn’t picking them up. Maybe it had some kind of a temporary network connection problem when trying to load the tags?

    In any case, let me know what you find.

    Thread Starter tdechangy

    (@tdechangy)

    all right, thx ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WP Rollback compatibility’ is closed to new replies.