• Resolved sffandom

    (@sffandom)


    I am using Subscribe2 on multiple Websites. The plugin has suddenly stopped working on ALL sites. Some of them are WordPress multiuser installations and some of them are single installations. The sites are scattered across several hosting accounts.

    Symptoms of the broken behavior include:

    Settings for the designated landing page mysteriously change.
    Attempts to subscribe/unsubscribe through the widget fail.

    In looking at the various support threads from early November 2013 it seems to me that the plugin has failed for multiple people and that must be due to something in the update process. You cannot have this many SQL databases suddenly just fail.

    I tried deleting and reinstalling the plugin on a small site. That did not fix the problem but it did delete the plugin’s data from the database.

    The various manual fixes provided in the recent support threads are not a solution for this widespread a problem.

    I see on the plugin page here at WordPress.Org that it is confirmed to be compatible only up to WP 3.6.1. Will there be a new update soon?

    http://wordpress.org/plugins/subscribe2/

Viewing 15 replies - 1 through 15 (of 34 total)
  • @sffandom,

    This is certainly very strange but I am not seeing this on my sites and those where I get paid to help.

    I don’t really see how it can be isolated to any upgrade code either as the last code release that necessitated any upgrade code to run was version 8.8 released in February 2013.

    I would need a more consistent and reproducible bug description in order to be able to track it down and issue a fix.

    Thread Starter sffandom

    (@sffandom)

    I can’t tell you what to do to create the problem because the only thing I did do on all these Websites was update the WordPress, plugins, and themes.

    The plugin broke with multiple themes, so I am sure it’s not a theme-specific issue.

    I have no way of isolating which plugin might have some sort of conflict with Subscribe2 if it is indeed a plugin conflict.

    I have disabled the plugin on all sites for now.

    Thread Starter sffandom

    (@sffandom)

    This issue is NOT resolved. If your way of dealing with these problems is to mark all complaints as resolved I will be sure to review your plugin in a most unflattering way.

    @sffandom,

    One thing to check (and this doesn’t apply to sinlge sites) is that Subscribe2 is not enabled site with on the Multisite installs or added as a ‘must use’ (MU) plugin.

    Instead it must be enabled site by site on multisite installs in order to correctly sandbox settings and subscribers between sub-blogs.

    Thread Starter sffandom

    (@sffandom)

    All implementations of the plugin were site-activated, not network-activated.

    @sffandom,

    I mark my threads as resolved to make sure I can keep track of them but I always check back on any that get replies. I do this because very few people use the resolve button to actually mark something as resolved when it actually is, so I put it to use for tracking purposes for myself.

    Of course you are at liberty to leave unflattering feedback if you wish but given that I code as a hobby, nothing related to my career in healthcare, that I share my efforts for free and that I generally respond to all posts on this forum with 12 hours of them being posted I would be very insulted by this.

    @sffandom,

    Are there any commonalities on the sites at all? Any other plugin used on every single site? Any core modifications?

    Thread Starter sffandom

    (@sffandom)

    No modifications to the core.

    Common plugins include:

    Akismet
    Stop Spammer Registrations
    Ad Injection
    Better Search
    Limit Login Attempts
    PC Robots.txt
    Rename Wp-login.php
    Search Meter
    Jetpack
    Whitelist IP for Limit Login Attempts
    Wordpress Editorial Calendar
    Wordpress Importer
    WP Social Bookmarking Light

    I don’t believe any other plugins are used across all these sites.

    All of these plugins (and yours) were installed months ago and functioned normally throughout that time. The problem only began a few days ago, apparently after I ran the updates.

    On some sites I have yet to update WordPress Editorial Calendar.

    @sffandom,

    Akismet, Stop Spammer Registrations and Limit Login Attempts are all fine as I use them personally or have deployed sites with them.

    The problem only began a few days ago, apparently after I ran the updates.

    What updates? You haven’t mentioned this previously. Did you update WordPress or Subscribe2? Both? Or other plugins / themes?

    Thread Starter sffandom

    (@sffandom)

    Mentioned it in the first message.

    I usually wait 2-3 days after a WordPress update is released because I know plugin and theme vendors will usually roll out new updates. So I performed mass updates on these blogs and many others on October 29.

    Since then I have only run a couple of updates on blogs that don’t use the Subscribe2 plugin.

    I have not encountered any other issues.

    @sffandom,

    If it is in the first message it isn’t explicit enough to help me debug. From the post above it would seem you updates WordPress – is that correct? Was it just WordPress? From what version to 3.7.1? Did you update Subscribe2 also or were you already running 9.0 at that time?

    Thread Starter sffandom

    (@sffandom)

    I updated EVERYTHING: WordPress, themes, and plugins. On some sites the previous version was 3.6.x (last version in that series). On a couple I had upgraded to 3.7.0 and it installed the 3.7.1 automatically.

    I only keep a record of when I manually update a Website. I don’t know when the automatic updates were applied. I assume within 24 hours of WP releasing 3.7.1.

    @sffandom,

    I wonder if it was simply related to the volume of updates being processed then. Perhaps we should try forcing the Subscribe2 upgrade() functions again. Do you wNt to give that a try.

    Thread Starter sffandom

    (@sffandom)

    I can give that a try. But I don’t know how to do it.

    As an aside, I have just noticed something odd on another site that does NOT use Subscribe2. I had a display issue with a site where I had installed the Rename Wp-Login.php plugin. By deactivating that plugin and reactivating it I was able to resolve the display issue.

    I don’t know if that is somehow related to what is happening with Subscribe2 but perhaps there is something in the core code that is messing with some plugins. I have no idea of what to look for.

    @sffandom,

    You certainly are getting some very bizarre issues at the moment.

    In order to re-call the upgrade code you need to take a 2 step process but it should be fairly simple.

    First we need to trick Subscribe2 into thinking it’s old. Go to the Plugins page in WordPress and deactivate Subscribe2. Then edit the plugin and in the main plugin file (subscribe2/subscribe2.php’ you’ll find the following line a little way into the code:
    define( 'S2VERSION', '9.0' );
    Change that to:
    define( 'S2VERSION', '2.0' );
    Then reactivate the plugin. Provided it activates okay (that means you’ve made the change correctly) it will look no different than before.

    The second step is to restore the version number by repeating the above steps. Deactivate, edit back to 9.0 and then reactivate. This will call all of the upgrade code and then we can see if that fixes any of the issues.

Viewing 15 replies - 1 through 15 (of 34 total)

The topic ‘Subscribe2 is NOT compatible with WP 3.7.1’ is closed to new replies.