paulodamian

@stodorovic

Your fix should be included in the plugin.

I added it a week ago and the problem did not happen again… until I updated the plug in to the version 1.5.7, just 20 minutes later the file corruption happened again. I have put the fix in place, but it will break on every update until some one include it on the plugin code

There are another 3 post talking about this issue, is a bug in the update.
Go to the other post to find a temporal fix until an update.

Settings -> WP SuperCache

I think that if you delete WP SuperCache via FTP/sFTP your entire site could stop working.
Try disabling WP SuperCache via your database

mcstar – On the sites that you cant login be sure that you are accesing a login page without GET parameters.

Go to yousiteUrl/wp-login.php and try

Ok, I have the same problem.

I will wait for a plugin update, but in the mean time the problem is present for pages with GET parameters if you have active the option:
“Don’t cache pages with GET parameters. (?x=y at the end of a url)”

In the options uncheck that feature and save, everything will work again.
But this is a temporal fix as that option is important for my site.

Ok, I have the same problem.

I will wait for a plugin update, but in the mean time the problem is present for pages with GET parameters if you have active the option:
“Don’t cache pages with GET parameters. (?x=y at the end of a url)”

In the options uncheck that feature and save, everything will work again.
But this is a temporal fix as that option is important for my site.

Ok, I have the same problem.

I will wait for a plugin update, but in the mean time the problem is present for pages with GET parameters if you have active the option:
“Don’t cache pages with GET parameters. (?x=y at the end of a url)”

In the options uncheck that feature and save, everything will work again.
But this is a temporal fix as that option is important for my site.

Did you checked the plugin settings?
What you are asking is an available configuration option.

I think that some one used your email in the form that is showed when the manage subscriptions page is visited by a not logged user.

Ok, I solved my problem.

Among other things specifics to my environment this is the code that I used to put the manage subscriptions options in a custom place:

global $wp_subscribe_reloaded;

if (isset($wp_subscribe_reloaded) && get_class($wp_subscribe_reloaded) == 'wp_subscribe_reloaded'){
    global $posts;
    $posts = $wp_subscribe_reloaded->subscribe_reloaded_manage();
    echo '<h2 class="entry-title">' . $posts[0]->post_title . '</h2>';
    echo $posts[0]->post_content;
}