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 WordPress database and can be easily exported to CSV format for further analysis (there is no import function). 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 – the goal can even update automatically when a % of your goal is reached. Petitions may also be configured to stop accepting new signatures on a specified date.
More information can be found at the official SpeakOut! WordPress petition plugin website: https://speakout.123host.net.au
- Albanian sq_AL Incomplete
- Arabic ar_AR
- Arabic ar (Faisal Kadri)
- Catalan ca (Alberto Canals)
- Czech cs_CZ (Petr Štepán, Michal Hradecký)
- Danish da_DK (A. L.)
- Dutch nl_NL (Kris Zanders, Petronella van Leusden)
- 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, Davide Granti, Simone Apollo)
- Norwegian nb_NO (Howard Gittela)
- Polish pl_PL (Damian Dzieduch)
- Portuguese (Brazil) pt_BR (Tel Amiel)
- Romanian ro_RO (Web Hosting Geeks)
- Russian ru_RU (Teplitsa)
- Serbian sr_SE (Mikhailo Matovic)
- 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.
Emailpetition Shortcode Attributes
The following attributes may be applied when using the ‘[emailpetition]’ shortcode
The ID number of your petition (required). To display a basic petition, use this format:
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”]’
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.
‘[emailpetition id=”1″ height=”500px”]’
‘[emailpetition id=”1″ height=”100%”]’
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″]’
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.
‘[emailpetition id=”1″ class=”alignright”]’
‘[emailpetition id=”1″ class=”style1 style2″]’
Signaturelist Shortcode Attributes
The ID number of your petition (required). To display a basic signature list, use this format:
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″]’
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”]’
The text that displays in the previous signatures pagination button. Default is <.
The text that displays in the next signatures pagination button. Default is >.
Display the number (as text) of signatures collected for a given petition:
The ID number of your petition (required).
Display the number (as text) of goal for a given petition:
The ID number of your petition (required).
Use the automatic installer. Or…
- Download and unzip the the plugin zip file.
- Upload the ‘speakout’ folder to your ‘/wp-content/plugins/’ directory
- Activate SpeakOut! Email Petitions through the “Plugins” menu in the WordPress admin.
Where is the FAQ?
Contributors & Developers
“SpeakOut! Email Petitions” is open source software. The following people have contributed to this plugin.Contributors
bug fix: petition without requires_confirmation and after form submit the signature count was showing “NaN” – thanks Thomas
bug fix: in some cases a new petition wasn’t loading content in the dashboard when editing it – thanks @papyrusdoc
- bug fix: if “confirm signatures” was enabled for a petition, then later disabled, signatures added but not confirmed (while enabled) weren’t counted.
- bug fix: two more database fields were missing – this was the source of the signature issues. Thanks to all who reported this and (hopefully) were patient for a fix.
- improvement: CSV can now optionally export only confirmed signatures – thanks Fredrik
- improvement: language updates
- bug fix: wrong version number for database update caused a database “duplicate field” error
- bug fix: two database field should have been added in last update
- bug fix: custom field 4 likely wasn’t working
- bug fix: on activation non-critical database error was thrown but only displayed if debug true
- bug fix: Viet Nam flag not displaying in signature list
- improvement: admin signature list made more readable replacing affirmative text with ✔
- improvement: added 2 custom checkboxes
- improvement: slowly implementing premium version. Free version will have reduced features but will still work – make a donation now (or if you have made one in the past) and you get the premium version free
- improvement: language files updated
- bug fix: debug code left behind, only affected expired petitions
- improvement: option to change thousands separator and decimal separator for different cultures e.g. 1,234.56 or 1.234,56 or 1 234.56 – find this in SpeakOut! > settings > petition form – thanks Caetano
- improvement: update admin CSS
- improvement: update language files
- bug fix: CSS directory didn’t upload with laste version
- bug fix: The word ‘anonymous’ wasn’t translated in petitions list – Thanks Miguel
- improvement: updated language files
- bug fix: missing language files…sigh…
- security fix: Thanks Erwan @WPScan
- improvement: updated “tested up to” to WP 5.9
- some bug fixes and improvements.
- bug fix: if email address is confirmed, it wasn’t added to 3rd party mailers – thanks Dan M @tahninial
- improvement: tweak default CSS so that opt-in text doesn’t wrap
- improvement: Australian English language file had some bizarre foreign language words
- improvement: updated “tested up to:” for WordPress 5.9
- improvement: implemented hcaptcha, an alternative to Google recaptcha
- improvement: updated signaturelist CSS so that table is 100% width – thanks Bahman
- improvement: better handling of required fields if form resubmitted
- bug fix: custom field 5 was not validating if set as required and in middle or bottom position on petition form – thank @pieter
- bug fix: there was no field to set the text to open/close an editable petition
- bug fix: if not collecting signatures and hiding email, options fields were disabled on any petition save – thanks @pieter
- bug fix: If it was enabled, the
custom field 5 requiredcheckbox wasn’t displaying the check after being saved. Thanks @pieter
- bug fix: didn’t include additional database fields for new install – thanks Dino
- Improvement: custom fields can now be excluded from the petition went it is sent to target – thanks Don G.
- Improvement: layout of checbox elements adjusted to match – thanks @nanuc
- Improvement: moved class selector from redundant span to parent div and removed span – thanks @nanuc
- Bug fix: petition title not being sent in reconfirm emails – thanks Vincent
- Improvement: fixed height of email field – thanks Luis
- Improvement: aligned checkbox if optin text flowed more than one line
- Improvement: changed text from “hide email from public” to “hide name from public” – wasn’t actually done in version 2.7.1
- Improvement: in Active Campaign integration setup, if no custom fields were active, “none” wasn’t displayed
- Improvement: removed superfluous “?”.
- Improvement: added “optin needs to be enabled” warning at top of integrations page
- Improvement: updates to language files