Subscribe2 Notifications to less than all subscribers

@alanyatvin

I haven’t noticed any problems. Have you got additional pages in the Email Log or does it stop at M then? When publishing new posts does the page return normally or do you get an error or white screen? Have you tried checking the server error logs?

@mattyrob

No additional pages in the log. Actually, they are in reverse order, with the first page of the log being the m’s and the last page being the A’s. Technically the log stops in the middle of the M’s, so not all of the M’s went out.

The page returned normally when publishing.

I am hosted on Yahoo, so I have no idea how to check the server error logs.

For the entire month, thru Nov 15th, post notice emails were being sent to my full subscriber list (1060). On Nov 19th I updated WP to 4.9, along with several plugins. On Nov 20th I published a new post and only 631 notice emails were sent. I published another last night and only 657 went out.

Also, the emails for these last two posts were not formatted as per the subscribe2 template for notices (which I have not changed in a year, or more). Instead, these notice emails were all run-on, with no line breaks or line spaces.

Other than the updates, I changed no settings and have no new plugins.

Any other thoughts?

Thanks,

Alan

PHP timeout?

@rehakk

Pardon my ignorance, but how would I determine if it is a PHP timeout and what would I do to fix?

Thanks,

Allan

@alanyatvin

I doubt it’s a PHP timeout as the page returns normally for you, usually a timeout would result in an apparent failures rather than an apparent success masking an actual failure.

This may aid you in locating any error_log files:

https://help.smallbusiness.yahoo.net/s/article/SLN20354

Have you upgraded Subscribe2 since before this issue started? Perhaps you could try downgrading if this might be an issue.

So, I rolled Subscribe2 back to v. 10.14 and republished the post. The notice emails have gone out to the entire subscriber list and the format problem has been cured. So, I am left to assume that there is an issue with v. 10.22.1. Maybe the imminent release of v. 11 will solve this, but I am incredibly gun shy, so I will not rush to upgrade immediately.