mkj2

OK, found the problem. It wasn’t the plugin, but a ridiculous content composer plugin that caused the wrong urls.

• This reply was modified 6 years, 7 months ago by mkj2.

Sorry, it is NOT included from the form_engine.php. Or at least: If I change something, nothing happens on the frontend. So, what’s going on here?

Usually it is. But you can’t depend on it. I use Thunderbird, and the confirmation link was not converted to a clickable link. Don’t know why, but it wasn’t. Furthermore, the line breaks were not converted to proper HTML line breaks. The result was something like this:

Hello, Thank you for signing our petition. Please confirm your email: https://example.com/?dkspeakoutconfirm=242f2b489c908b9f&lang=

By the way, suddenly WordPress stopped sending the confirmation emails. I couldn’t figure out why. Then I found that due to an autofill mistake a text was saved instead of a proper email (settings > confirmation emails > sender email). If you don’t fill in a fully valid email address, it won’t send any email at all. Might be a good idea to add a warning and save youself some trouble. ??

• This reply was modified 6 years, 9 months ago by mkj2.
• This reply was modified 6 years, 9 months ago by mkj2.

I get your point. However, you wouldn’t believe how, say, unexperienced users are. To manually copy a link and paste it in the browser is without any doubt some challenge for many. I have customers who asked me: What is an URL? Where should I put it?

Overwriting core files is always a bad idea, since it is not update-safe. A hook would be the way to go.

Don’t get me wrong: I appreciate your effort and support and thank you very much for sharing this plugin with us. These are just some ideas for improvements (from the user’s point of view).

Thanks a lot. Almost there. I added the <a> and <p> tags. The textarea line breaks were not converted to <br />. Inline styles are working, too. Nice! The <a> tag is quite important, in my humble opinion. Is there a reason not to include the <p> tag? Anybody who can write HTML will probably know how to use is.

Thanks for the support! No need for a complex email, but a pretty one. ?? These days, users expect large buttons and stuff. Would you mind posting the mod here? So we wouldn’t have to wait for the update.

Thank you!

Awesome, thank you! Allow me to be greedy! Today, people are used to high quality HTML emails. A simple HTML email is better than plain text. However, it would be much more elegant, if we could add CSS and complex HTML. Could you tweak the strip_tags command so that even tables and CSS would be accepted? At least tables and inline css styles should be possible. That’s enough for acceptable HTML emails.

I didn’t mean “admin email” but “confirmation email”. With this feature enabled, not only an additional email input field is added to the form. The submitter will receive a confirmation email with a link. You can then return the submitter to the signatures list that will already show the new entry. Much better UX in my opinion.

Ah, not quite there. I’ve just tested the widget form. The lightbox overlay shows a checkbox (show honorific) but not the dropdown itself. In addition to that, there is a shortcode [your signature] on the left side. See here my test installation with no other plugins activated and the plugin untouched:
https://demo.my-blog-shop.de/
Thank you!

We use standard p, br and a tags in the textarea where we can change the text for the confirmation email (SpeakOut! > settings > confirmation emails) I change the serialized data directly in the options table. However, this is not a solution. Any changes in the settings would overwrite this.

Sounds pretty good. Thanks!

Oh, I have to apologize. I used the shortcode in a textwidget. Totally overlooked the petition widget. Sorry, my mistake.

I had changed the widget to a simple link to the petition page, since the site is already live. This is why you couldn’t see the code. The widget works perfectly fine now.

Thanks a lot!

Thank you very much!

I’ve just checked this in my test installation: WP 4.9.4, Twenty16, no other plugins activated. Same problem. The widget is simple not working.