mrmacross

Addendum:
Sorry for continuing on, but this thought also occurred to me. Your current spammer control could also lead to a DoS attack. If a site is meant to serve a particular region or clientele, could not a saboteur/competitor possibly obtain a list of relevant addresses and submit them through the subscription service indiscriminately? If someone were to receive an unexpected/unsolicited email about subscribing to the site, they would likely trash it. But, if the site is relevant to their life in some manner, they may come across the site naturally some time down the road and then be unable to subscribe due to your current settings. And they would receive very little help in figuring out why this happens.

While you’re still having internal debates on how to handle spammers, perhaps you could add the link https://subscribe.wordpress.com to your error/success message (the message that users/blog owners have no control over)? Despite my test addresses possibly falling into the single use bucket, I still received Success messages when I re-submitted the address through the form.

It seems like quite a service gap to ask someone to hold on to an old confirmation message – maybe the first time it went to their junk folder. I mean, the first confirmation message may have been sent a year ago! Perhaps you just need to have a timeout setting to deal with spammers? One message per day to potential subscribers? Your obviously keeping a record of all attempts so adding a timeout wouldn’t be too much extra work/extra data.

And just an additional note to further illustrate the situation – I have tried the subscribe.wordpress.com link above and entered in one of my test addresses. Lo and behold, there was a pending subscription notice from the 10th of January. I never received that email! It is not in my Deleted folder, which contains messages older than the 10th, and it is not in my Inbox. So, what is a user to do? I re-submitted that address multiple times, and due to your policy of course, never received an additional message. From the Subscribe page, I deleted the Pending activation and then re-submitted the email address and this time I received a confirmation email! That’s a lot of work to put a potentially unsavvy web user through. So how do you account for all of the potential gaps in the email chain? Again, I suggest that you should alter your anti-spam policy in some meaningful way perhaps using a timeout feature to make addresses valid again. And again, I suggest an interim solution of adding a small note about the Subscribe URL in your Success/Error messages which are built in to the function.

I will use your private support form to give you the viewing password to my site so that you may look at the subscribe feature which is on the front page.

Thanks for your help, I appreciate that you have at least communicated with myself (and angelagoodnight).

I would also like to add that I have noticed that a previous address that has been sent a confirmation email will no longer receive confirmation emails if the address is subscribed again – even if they didn’t confirm the first time.

The confirmation email is to prevent spam, but what if a spamee later on decides they want to join the WordPress site? If they can’t get another confirmation message they will never be able to join.

We’re having a similar problem with the site I’m developing at https://www.volunteeringsunshinecoast.com.au/vsc. I get Success messages when I put in an email address to subscribe, but 2 of 4 addresses have not received any confirmation messages and I’ve tried multiple times over many days. I’d prefer not to post any personal details such as the email addresses or the temporary viewing password (the site is in development for a few more days before going public).

Please contact me privately through my account if you need something more than the domain in which the blog is being used. Or give me an address I can send the information to directly. Thanks.

My project uses Suffusion. Probably should have added that.

This seemed to be working fine under the last version of AMR.

Just for a little further information, we have also decided to disable AMR Shortcode. I have a version of my site on InstantWP and a version hosted on an Internet webhost. I suspect there may be some PHP configuration difference as I could not reproduce the error that I was getting consistently on the Internet host on my InstantWP instance. Everything worked fine in InstantWP.

Hello,

we’ve come across the same problem. I think it has to be related to the AMR plugin because we only get the error on pages which we are using the shortcode. Any chance of an update addressing this issue?

Sidebar Shortcodeswith sidebarid Shortcodes empty or not defined.
Widget Blog Subscriptions (Jetpack) not in sidebar with id Shortcodes and with name Shortcodes

Sidebar Shortcodeswith sidebarid Shortcodes empty or not defined.
Widget Calendar not in sidebar with id Shortcodes and with name Shortcodes

Warning: Cannot modify header information – headers already sent by (output started at /home/suncoast/public_html/vsc/wp-content/plugins/amr-shortcode-any-widget/amr_shortcode_any_widget.php:147) in /home/suncoast/public_html/vsc/wp-admin/post.php on line 229

Warning: Cannot modify header information – headers already sent by (output started at /home/suncoast/public_html/vsc/wp-content/plugins/amr-shortcode-any-widget/amr_shortcode_any_widget.php:147) in /home/suncoast/public_html/vsc/wp-includes/pluggable.php on line 896