Kreg Wallace

Emilie,

I checked the page in a few browsers and the sign now button seems to be working fine.

For the people not receiving confirmation emails, this may be because their email provider does not support email sent from PHP’s mail() function, which WordPress uses to send email. Email providers like AOL and Hotmail are notorious for this. The solution is to install the WP Mail SMTP plugin, which will redirect email sent by WordPress through your server’s SMTP configuration. This is covered a little further on the FAQ page for my plugin.

There isn’t a way to resend confirmation mails yet. The confirmation links for your site would be in the format:

https://www.tendance-allaitement.fr/?dkspeakupconfirm=9cc3401986b5b5d4

where only that last number will be unique for each signature. You can get this unique confirmation code out of the exported CSV files and reconstruct the confirmation links by replacing the number above with each confirmation code. I know that’s a big hassle though and I may get a resend confirmation mails feature working in the future.

If you know the email has been misspelled and you know what the correct spelling is, then you could just delete the incorrect signature and sign the person up again using the correct info.

It does seem unlikely to me that someone would sign the petition with incorrect information, but that you would actually know what the correct information is. I think it’s more likely that someone wanted to sign the petition, but used an incorrect email address because they don’t want to be contacted by anyone about their signature.

If you don’t want to require that people confirm their signatures, then you might be best to leave the ‘require email confirmations’ option off.

Hi Julia.

That’s not something I’m working on right now, but I may try to find a better solution for sending mail to a list of recipients in the future.

Another user emailed me on this… It seems that IE won’t allow values greater than 3 digits in ordered lists. So 999 is the limit for now.

I’ll be changing the way the signature list displays to use a table rather than an ordered list. While you’re waiting for the new version of the plugin to come out, I suggest setting the recent signatures to display only 999 or less.

For the benefit of others, Jayson and I sorted this one out. Seems the problem was with the use of WP Super Cache plugin. The cached pages don’t pull a dynamic signature count from the database, so it takes awhile for the new signatures to show up on the public list.

Thanks Oren,

I’m getting the RTL language support sorted out now. I’ll have that and your Hebrew localization file in the next release.

I noticed that all of the petitions linked to in the comments above are displaying enormously long lists of signatures. Maybe returning the setting for the number of latest signatures to display back to something near the default of 50 would keep some older versions of Internet Explorer from freaking out.

I’ll take a look at alternate ways of displaying the signatures for a future release.

I’ve updated the plugin to version 1.2.1 and I think this update might fix the problem you’re experiencing.

I can’t seem to duplicate the problem. The page loads fine for me and I haven’t had reports of anything similar from other users.

when you run the page through an HTML validator, it shows that there is a character in one of the comments that doesn’t map to UTF-8. Seems to be something in the comment signature from Vera of Ukraine. I’d try editing any odd characters out of that comment and see if it helps.

Not sure exactly what you mean by “hangs”. Can you give a more detailed description of what you’re seeing on the page?

I visited the link you provided in IE 9 and everything appears to be working fine.

There’s no easy way to add custom fields. You can tell users put their zip code in the address textarea though.

I’m thinking of adding a new optional field for this in a future release.

Hi Steve,

Another person had a similar problem and fixed it with an .htaccess edit. See thread here.

Most likely, you have some code that is altering the URL in the submit button link. Could you post a link to a page where this problem is showing up?

I’m not sure how effective it would be to just resend someone another copy of the confirmation email that they ignored before. Instead, you might try using the subject line tip described in this recent article (just change the subject line to “Please confirm your email address”).

I think I’m going to change the default subject line to this in the next update.

Interesting issue… hadn’t seen that one before, but I’m glad you found a solution.

Nice work. Glad you got that to work for you. Hopefully I’ll be able to get a widget working for the plugin soon to relieve you of the need for the hack.