SpeakOut! Email PetitionsbySteve D - 123host.com.au

SpeakOut! Email Petitions allows you to easily create petition forms on your site.

When visitors to your site submit the petition form, a copy of your message will be sent to the email address you specified e.g. your mayor. They can also choose to have the email BCC’d to themselves (default). The petition message will be signed with the contact information provided by the form submitter. After signing the petition, visitors will have the option of sharing your petition page with their followers on Facebook or Twitter.

Signatures are stored in the database and can be easily exported to CSV format for further analysis. You may set a goal for the number of signatures you hope to collect and then watch as a progress bar tracks your petition’s advance toward it’s goal. Petitions may also be configured to stop accepting new signatures on a specified date.

This plugin is a fork of the speakup plugin that was quite good but needed updates and has been abandoned. Current versions of SpeakOut! include an importer to migrate from speakup.

Localizations

• Albanian sq_AL Incomplete
• Arabic ar_AR (Asem Alzoubi)
• Catalan ca (Alberto Canals)
• Czech cs_CZ (Petr Štepán, Michal Hradecký)
• Danish da_DK (A. L.)
• Dutch nl_NL (Kris Zanders)
• Finnish fi_FI
• French fr_FR
• German de_DE (Hannes Heller, Armin Vasilico, Andreas Kumlehn, Frank Jermann)
• Hebrew he_IL (Oren L)
• Korean ko_KO (Paul Lawley-Jones)
• Icelandic is_IS (Hildur Sif Thorarensen)
• Italian it_IT (MacItaly)
• Norwegian no_NO & nb_NO
• Polish pl_PL (Damian Dzieduch)
• Romanian ro_RO (Web Hosting Geeks)
• Russian ru_RU (Teplitsa)
• Slovak sk_SK (@Beata)
• Slovenian sl_SI (MA-SEO)
• Spanish es_ES
• Swedish sv_SE (Susanne Nyman Furugård @sunyfu)

If you would like to request or contribute a specific translation not listed above, visit the SpeakOut! Email Petitions website and use the contact form.

1.20.3.1

• Improvement – made “Country” placeholder translatable

1.20.3

• Bug fix – added placeholder for Country field

1.20.2

• Bug fix – database fields weren’t being created for new installs
• Bug fix – recaptcha worked well. However if it wasn’t enabled people couldn’t sign. Kludge workaround to keep things going.
• Bug fix – copied Norwegian language file from nb_NO to no_NO
• Improvement – minor rearrangement of settings page

1.20.1.1

• Bug fix – left code out of 1.20.1

1.20.1

• Bug fix – a site has a javascript error related to recaptcha, workaround for that.

1.20.0

• Improvement – if custom field is displayed, label is required
• Improvement – individual address elements can be required or not – thanks @retrocool
• Improvement – support for recaptcha2 – enable on dashboard > SpeakOut! > settings page – thanks to @Audun and others for prodding me ;o)
• Improvement – updated Czech translation. Thanks Michal.
• Improvement – added Japanese translation – needs work, can you help?
• Improvement – updated translations

1.19.4

• Bug fix – CSS file not loading on admin settings page

1.19.3.1

• Bug fix – one updated file not included in 1.19.3

1.19.3

• Bug fix – it seems that the core WP bug I have been wrestling with affects different versions of WP differently so I have rolled it back
• Bug fix – typo was causing a PHP warning in ajax.php
• Bug fix – replace PHP count() with native wpdb->num_rows to eliminate PHP warnings

1.19.2

• Bug fix – new petition not saving
• Bug fix – database update improved

1.19.1

• Bug fix – Still getting the menus right…sorry…

1.19.0

• Improvement – URL can be set (on edit petition page) for redirection after successful signing.
• Bug fix – cause of menu bug discovered (duplicate menu slugs) and remedied.

1.18.3

• Bug fix – seems there is a bug in WordPress https://core.trac.wordpress.org/ticket/48599 that causes an error to be thrown, possibly only on some versions of PHP. It isn’t affecting the petition, it is caused in the rendering of menus in the dashboard – I have added a workaround for now. I am also learning lots about the guts of WordPress ?

1.18.2

• Bug fix – I introduced a future bug in 1.17.8 when preparing for WP 5.3 by not wrapping a number in quotes. Weirdly it only affected 3 sites (so far) and I couldn’t reproduce it. This was really hard to track down and I couldn’t have done it without the help of @fish911

1.18.1

• Bug fix – in petition, plural of the word “signature” not working in some languages
• Bug fix – CSV download button wasn’t displaying on signature page load
• Improvement – Tidier heading on signature page with better information
• Improvement – added Catalan language – thanks Alberto

1.18.0

• Bug fix – basic theme wasn’t hiding petition message
• Improvement – tidied up code and styles for check boxes below petition

1.17.9.1

• Bug fix – required custom field not working properly (but it did on my test site…really!)

1.17.9

• Bug fix – Word “location” for custom field setup wasn’t translated
• Improvement – now possible to have custom field be required – thanks Bahman
• Improvement – Code tidied up
• Improvement – translation updates

1.17.8

• Bug fix – squashed a future bug that would have shown up in WP 5.4 – thanks @davidbinda
• Bug fix – missing space in label tag
• Bug fix – missing space in some translations of “Yes, I accept your privac policy” – Thanks Stijn
• Bug fix – unwrap those pesky opt-in checkbox lines

1.17.7

• Improvement – updated styles, especially for basic theme.
• Improvement – some UI tweaks in petition and dashboard
• Improvement – removed .less style sheets

1.17.6

• Bug fix – prevent saviing values of 0 or blank in settings > admin display tab
• Improvement – Tidied up petition options right column in admin area

1.17.5

• Bug fix – setting page not working because I copied the wrong code from my development site to a plugin page :o(

1.17.4

• Bug fix – when using URL to redirect to specific petition e.g. ?petition=10, the signature count was showing total for the first petition instead.
• Bug fix – when using URL to redirect to specific petition e.g. ?petition=10, the widget was displaying the first petition

1.17.3

• Bug fix – custom message wasn’t being displayed after signing – thanks @lucapoe

1.17.2

• Improvement – better handling of drop down menu on signatures page Thanks @Donna4u2
• Improvement – better display of signature list. Only the custom field wraps.
• Improvement – option to hide social media sharing buttons
• Improvement – removed much of the old changelog to reduce the size of this file. Legacy updates can be found at https://speakout.123host.net.au/changelog

1.17.1

• Bug fix – “display petition message” checkbox not checked by default
• Bug fix – database field added to wrong table
• Improvement – added a -fi.mo language file as well as a -fi_FI.mo – ome day I might understand this whole language file thing.
• Improvement – update language files.

1.17.0

• Improvement – petition message can now be displayed (default) or hidden, option located in right column when editing petition. Thanks to people who suggested this.
• Improvement – if custom field is active, the contents are now displayed in the admin signature list. Thanks @fredygiro
• Improvement – added support for Anedot.com fundraising form. Enable this in the petition settings page. It adds a tab to the settings page. The donation form is then displayed as part of the success message when someone signs the petition. Thanks @DougJoseph for the idea and the code.
• Improvement – added de_DE_formal language as it seems to be a thing – I can’t find any info about this.
• Improvement – updated language files

1.16.4

• Improvement – Honorific now included in CSV export of signatures – thanks Peter

1.16.3

• Bug fix – return URL wasn’t saving Thanks @dougjoseph
• Bug fix – allow + sybmol in email addresses – did you know that if your email is [email protected], [email protected] works and when providing your details doing something like [email protected] can identify if people are selling your email address (SpeakOut! isn’t).
• Improvement – tidied up the behaviour when someone clicks confirmation email and returns to site.
• Improvement – cleaned up some inconstistent text formatting

1.16.2

• Improvement – tweaked CSS for checkboxes on petition so they lign up more neatly
• Bug fix – Privacy policy check box was submitting petition even if it wasn’t checked. Thanks @mistercurtain

1.16.1

• Improvement: fixed incorrect checkbox alignment in basic CSS file – thanks @daymobrew
• Updated to WordPress 5.2.3

1.16.0

• Improvement: changed field labels to placeholders, reduces size of petition. Required fields now have no label and a pale red border rather than a red asterisk after the label. The border colour can be adjusted in theme-default.css, find the :required element. Thanks for the pointer @mistercurtain
• updated widget, sometimes changes to main petition get forgotten in widget

(https://speakout.123host.net.au/changelog)

Emailpetition Shortcode Attributes

The following attributes may be applied when using the ‘[emailpetition]’ shortcode

id

The ID number of your petition (required). To display a basic petition, use this format:
‘[emailpetition id=”1″]’

width

This sets the width of the wrapper ‘

<

div>’ that surrounds the petition form. Format as you would a width rule for any standard CSS selector. Values can be denominated in px, pt, em, % etc. The units marker (px, %) must be included.

To set the petition from to display at 100% of it’s container, use:
‘[emailpetition id=”1″ width=”100%”]’

A petition set to display at 500 pixels wide can be achieved using:
‘[emailpetition id=”1″ width=”500px”]’

height

This sets the height of the petition message box (rather than the height of the entire form). Format as you would a height rule for any standard CSS selector. Values can be denominated in px, pt, em, % etc. The units marker (px, %) must be included.

A few notes on using percentages:
Using a % value only works when the “Allow messages to be edited” feature is turned off—because the petition message will be displayed in a ‘

<

div>’. When “Allow messages to be edited” is turned on, the petition message is displayed in a ”, which cannot be styled with % heights. Use px to set the height on petitions that allow message customization.

To set the message box to scale to 100% of the height of the message it contains, use any % value (setting this to 100%, 0%, 200% or any other % value has the same result). Use px if you want the box to scale to a specific height.

Examples:
‘[emailpetition id=”1″ height=”500px”]’
‘[emailpetition id=”1″ height=”100%”]’

progresswidth

Sets the width of the outer progress bar. The filled area of the progress bar will automatically scale proportionally with the width of the outer prgress bar. Provide a numeric value in pixels only. Do not include the px unit marker.

To display the progress bar at 300 pixels wide, use:
‘[emailpetition id=”1″ progresswidth=”300″]’

class

Adds an arbitrary class name to the wrapper ‘

<

div>’ that surrounds the petition form. Typically used to assign the alignright, alignleft or aligncenter classes to the petition in order to float the petition form to one side of its container. To assign multiple classes, separate the class names with spaces.

Examples:
‘[emailpetition id=”1″ class=”alignright”]’
‘[emailpetition id=”1″ class=”style1 style2″]’

Signaturelist Shortcode Attributes

id

The ID number of your petition (required). To display a basic signature list, use this format:
‘[signaturelist id=”1″]’

rows

The number of signature rows to display in the table. This will override the default value provided on the Settings page. To display 10 rows, use:
‘[signaturelist id=”1″ rows=”10″]’

dateformat

Format of values in the date column. Use any of the standard PHP date formating characters. Default is ‘M d, Y’. A date such as “Sunday October 14, 2012 @ 9:42 am” can be displayed using:
‘[signaturelist id=”1″ dateformat=”l F d, Y @ g:i a”]’

prevbuttontext

The text that displays in the previous signatures pagination button. Default is <.

nextbuttontext

The text that displays in the next signatures pagination button. Default is >.

signaturecount Shortcode

Display the number (as text) of signatures collected for a given petition:

id

The ID number of your petition (required).
‘[signaturecount id=”3″]’

signaturegoal Shortcode

Display the number (as text) of goal for a given petition:

id

The ID number of your petition (required).
‘[signaturegoal id=”3″]’