Tim Pritlove

Podlove -> Podcast Settings -> Directory

The PSB is meant to subscribe with Podcast Clients. Subscribe by e-mail is a totally different functionality that is highly podcast-specific and can’t be easily integrated.

Oops, I must correct myself: looks like jobs are going through after having switched to the new beta version. Have you made changes to the Dropbox API code in that version?

• This reply was modified 7 years, 5 months ago by Tim Pritlove.

I have got 0,87 TB of free space. Backup files are around 2GB.

Can it be a PHP file size limitation? 2GB could to be a critical boundary I guess.

File System is ZFS so that shouldn’t be a problem.

Tried the current beta, no change.

• This reply was modified 7 years, 5 months ago by Tim Pritlove.

I put in the fix and restartet the job. It still can’t be completed. Log says:

`
[12-Jun-2017 17:04:49] Upload beendet: Es wurden 3 GB hochgeladen.
[12-Jun-2017 17:04:52] FEHLER: Gr??e der lokalen und der hochgeladenen Datei ist nicht identisch.
[12-Jun-2017 17:04:52] 2. Versuche, das Backup zur Dropbox zu senden …
[12-Jun-2017 17:04:52] Lade 4 MB Daten hoch
[12-Jun-2017 17:04:53] Authentifiziert mit der Dropbox von: nn
[12-Jun-2017 17:04:53] Hochladen zur Dropbox hat begonnen …
[12-Jun-2017 17:04:53] FEHLER: Ausnahme eingefangen in Error: Call to undefined method BackWPup_Destination_Dropbox_API_Request_Exception::error()
[12-Jun-2017 17:04:54] 3. Versuche, das Backup zur Dropbox zu senden …
[12-Jun-2017 17:04:54] Lade 4 MB Daten hoch
[12-Jun-2017 17:04:54] Authentifiziert mit der Dropbox von: nn
[12-Jun-2017 17:04:54] Hochladen zur Dropbox hat begonnen …
[12-Jun-2017 17:04:55] FEHLER: Ausnahme eingefangen in Error: Call to undefined method BackWPup_Destination_Dropbox_API_Request_Exception::error()
[12-Jun-2017 17:04:56] FEHLER: Schritt abgebrochen: zu viele Versuche!
[12-Jun-2017 17:04:56] Eine alte Log-Datei gel?scht
[12-Jun-2017 17:04:56] FEHLER: Job mit Fehlern beendet in 7131 Sekunden. Um eine korrekte Ausführung zu gew?hrleisten, musst du die Fehler beheben.
`

Maybe this is unrelated to the bug described in this thread?

I am experiencing a similar problem. What was the solution here?

Thanks for reporting. We’ll look into it.

Discussion continued on https://github.com/stcr/subscribe-to-comments-reloaded/issues/104

This looks like an incompatibility with WordPress multisite installations. The plugin is looking for the blog-local table wp_5_subscribe_reloaded_subscribers but in the database there is only a global wp_subscribe_reloaded_subscribers table to be found.

Is the plugin expected to work with Multisite installations at all?

Indeed: there is something to be found. I include all error messages that directly relate to a single email address (which I have anonymized):

[Mon Jun 22 09:16:24.099497 2015] [:error] [pid 27704] [client 31.25.121.188:65459] WordPress-Datenbank-Fehler Table 'db_4567_2_jjt.wp_5_subscribe_reloaded_subscribers' doesn't exist f\xc3\xbcr Abfrage SELECT salt, subscriber_unique_id FROM wp_5_subscribe_reloaded_subscribers WHERE subscriber_email = '[email protected]' von wp_new_comment, do_action('comment_post'), call_user_func_array, wp_subscribe_reloaded->new_comment_posted, wp_subscribe_reloaded->notify_user, wp_subscribe_reloaded->get_subscriber_key, referer: https://freakshow.fm/fs156-grosses-loch-alleine-reicht-nicht
[Mon Jun 22 10:37:04.479767 2015] [:error] [pid 38246] [client 62.30.150.238:56597] WordPress-Datenbank-Fehler Table 'db_4567_2_jjt.wp_5_subscribe_reloaded_subscribers' doesn't exist f\xc3\xbcr Abfrage SELECT salt, subscriber_unique_id FROM wp_5_subscribe_reloaded_subscribers WHERE subscriber_email = '[email protected]' von do_action('wp_ajax_dim-comment'), call_user_func_array, wp_ajax_dim_comment, wp_set_comment_status, do_action('wp_set_comment_status'), call_user_func_array, wp_subscribe_reloaded->comment_status_changed, wp_subscribe_reloaded->notify_user, wp_subscribe_reloaded->get_subscriber_key, referer: https://freakshow.fm/wp-admin/edit-comments.php?p=8833&approved=1
[Mon Jun 22 12:01:53.745479 2015] [:error] [pid 49535] [client 62.30.150.238:59032] WordPress-Datenbank-Fehler Table 'db_4567_2_jjt.wp_5_subscribe_reloaded_subscribers' doesn't exist f\xc3\xbcr Abfrage SELECT salt, subscriber_unique_id FROM wp_5_subscribe_reloaded_subscribers WHERE subscriber_email = '[email protected]' von do_action('wp_ajax_replyto-comment'), call_user_func_array, wp_ajax_replyto_comment, wp_new_comment, do_action('comment_post'), call_user_func_array, wp_subscribe_reloaded->new_comment_posted, wp_subscribe_reloaded->notify_user, wp_subscribe_reloaded->get_subscriber_key, referer: https://freakshow.fm/wp-admin/edit-comments.php?p=8833&approved=1
[Mon Jun 22 13:15:58.680889 2015] [:error] [pid 58973] [client 2001:4dd0:ff00:9656:8904:98b1:6a19:336a:65484] WordPress-Datenbank-Fehler Table 'db_4567_2_jjt.wp_5_subscribe_reloaded_subscribers' doesn't exist f\xc3\xbcr Abfrage SELECT salt, subscriber_unique_id FROM wp_5_subscribe_reloaded_subscribers WHERE subscriber_email = '[email protected]' von wp_new_comment, do_action('comment_post'), call_user_func_array, wp_subscribe_reloaded->new_comment_posted, wp_subscribe_reloaded->notify_user, wp_subscribe_reloaded->get_subscriber_key, referer: https://freakshow.fm/fs156-grosses-loch-alleine-reicht-nicht
[Mon Jun 22 17:22:54.740485 2015] [:error] [pid 91031] [client 89.144.207.161:65114] WordPress-Datenbank-Fehler Table 'db_4567_2_jjt.wp_5_subscribe_reloaded_subscribers' doesn't exist f\xc3\xbcr Abfrage SELECT salt, subscriber_unique_id FROM wp_5_subscribe_reloaded_subscribers WHERE subscriber_email = '[email protected]' von wp_new_comment, do_action('comment_post'), call_user_func_array, wp_subscribe_reloaded->new_comment_posted, wp_subscribe_reloaded->notify_user, wp_subscribe_reloaded->get_subscriber_key, referer: https://freakshow.fm/fs156-grosses-loch-alleine-reicht-nicht
[Mon Jun 22 18:07:10.239547 2015] [:error] [pid 97004] [client 84.114.142.63:46725] WordPress-Datenbank-Fehler Table 'db_4567_2_jjt.wp_5_subscribe_reloaded_subscribers' doesn't exist f\xc3\xbcr Abfrage SELECT salt, subscriber_unique_id FROM wp_5_subscribe_reloaded_subscribers WHERE subscriber_email = '[email protected]' von wp_new_comment, do_action('comment_post'), call_user_func_array, wp_subscribe_reloaded->new_comment_posted, wp_subscribe_reloaded->notify_user, wp_subscribe_reloaded->get_subscriber_key, referer: https://freakshow.fm/fs156-grosses-loch-alleine-reicht-nicht

Extra information: this content caused the problem:

s:603:”a:2:{i:0;s:174:"<div class="updated"><h3>Subscribe to Comments Reloaded Important Notice</h3><p>The information in your database has been sanitize to prevent the raw html messages.</p></div>";i:1;s:261:"<div class="updated"><h3>Wichtiger Hinweis</h3><p>The creation of table wp_subscribe_reloaded_subscribers was successful.</p><p>This new table will help to add your subscribers email address safer and prevent the Google PII violation.</p></div>";}”;

Somehow the array information got double escaped so that the whole array was stored a string.

I found the problem and I have a solution.

Problem is that the plugin stores information in the wp_options table in a field with option_name = “subscribe_reloaded_deferred_admin_notices” and that this content does not get properly migrated as this value was a string once and is expected to be an array now.

Deleting all entries with option_name = “subscribe_reloaded_deferred_admin_notices” in wp_options (and in all wp_<n>_options tables if you have a multisite installation) made the error go away.

Solution for plugin developer: either sanitize data from wp_options or invalidate that cached information after upgrade.

I am running on PHP 5.6.7

A future update will allow adjustment of the button colour.

Great. Thanks.