Subscriber not found, it probably has already been removed. No further actions a

[DavidAtSuncast]

Updated and now get this when opening the newsletter page: “Subscriber not found, it probably has already been removed. No further actions are required.”

WP v6.2.2. Newsletter v7.8.2. All plugins updated. Something simple? Bug in the update?

[Elf Zig]

Same.

[Stefano]

Thank you for reporting, we’ll check it asap.

[Stefano]

Hi, that message is usually associated to the cancellation process. Clicking which link brings to the message? A link inside the newsletter? The “view online” link?

[Elf Zig]

Not by clicking a link – just by opening the newsletter subscription page.

[DavidAtSuncast]

What Elf Zig said.

[oVerRider]

Same here it shows everywhere where [newsletter] shortcode is used. I have also custom newsletter box on some parts of my website and when subscribing it shows white page with those errors:

Warning: Invalid argument supplied for foreach() in /home/r16023/domains/xxx/public_html/wp-content/plugins/newsletter/includes/module-base.php on line 401

Warning: Cannot modify header information – headers already sent by (output started at /home/r16023/domains/xxx/public_html/wp-content/plugins/newsletter/includes/module-base.php:401) in /home/r16023/domains/xxx/public_html/wp-content/plugins/newsletter/subscription/subscription.php on line 413

Warning: Cannot modify header information – headers already sent by (output started at /home/r16023/domains/xxx/public_html/wp-content/plugins/newsletter/includes/module-base.php:401) in /home/r16023/domains/xxx/public_html/wp-includes/pluggable.php on line 1427

Warning: Cannot modify header information – headers already sent by (output started at /home/r16023/domains/xxx/public_html/wp-content/plugins/newsletter/includes/module-base.php:401) in /home/r16023/domains/xxx/public_html/wp-includes/pluggable.php on line 1430

(site domain changed to xxx) However the email will be still subscribed, but user gets that error message.

[Stefano]

Hi, it is probably related to a not defined array, on next release tomorrow it should be fixed. Please, disbale the WP_DEBUG in your blog, changing the definition inside the wp-config.php file.

It is always recommended to keep the WP_DEBUG to false on a live site.

[oVerRider]

Thanks for the tip! However checked wp-config.php file and it was set to false. What makes you think it was set to true?

[Stefano]

Those kinds of PHP warnings should not be shown if it is set to false, but every PHP installation can have different server settings.

[oVerRider]

Thanks for the update release. The issues are fixed now.

[Elf Zig]

Yep, confirmed. Thanks for the quick fix!

[ErinRadoAuthor]

When will this bug be fixed?

I’m doing a show this weekend, and I may need to use a different form.

[DavidAtSuncast]

Yes, fixed!
Thank you!

[Author]

Posts