Sabaoh

<p>Members Category is an add-in for WP-Members™ plugin. It has tested with WordPress® 3.3.2 and WP-Members™ 2.7.4. With Members Category plugin, you can choose some categories to be restricted and other categories to be free access. In front page and archive page, it suggests masking any restricted contents, too.</p>
<h4>Features:</h4>
<ul>
<li>Apply WP-Members’™ restriction by some categories.</li>
<li>Can mask all restricted contents from the front page and archive pages.</li>
</ul>
<h3>For more information</h3>
<p>Please visit http://sabaoh.sakura.ne.jp/wordpress/ . In Japanese only.<br />
If you need information in English, please contact to mailto:age.yamada@kxa.biglobe.ne.jp .</p>


Members Category

Members Category is an add-in for WP-Members™ plugin that restricts specified categories to registered users.

Andrew

RopeSwingHld

SpeakOut! Steve

<p><strong>SpeakOut! Email Petitions</strong> allows you to easily create petition forms on your site.</p>
<p>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 x.</p>
<p>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.</p>
<p>The free version includes the core features needed to run a successful petition. For those who need more, the <strong>Pro version</strong> unlocks the ability to run unlimited campaigns and provides additional tools, such as an email sharing option and expanded integration with third-party mailing services.</p>
<p>More information about the plugin and how to upgrade to the fully featured Pro version can be found at the official <a href="https://speakoutpetitions.com" rel="nofollow ugc">SpeakOut! WordPress petition plugin website</a>.</p>
<h3>4.6.5.1</h3>
<p>This is a critical security patch. Please update immediately to protect your user data.</p>
<h3>4.6.5</h3>
<ul>
<li>Bugfix: address misc warnings.</li>
</ul>
<h3>4.6.4</h3>
<ul>
<li>Bugfix: fix anonmyous record keeping issue. </li>
<li>Bugfix: fix nonce issue with some admin pages causing permision errors.</li>
</ul>
<h3>4.6.3</h3>
<p>Fix bad cache.</p>
<h3>4.6.2</h3>
<p>Fix php warning regarding missing options.</p>
<h3>4.6.1</h3>
<ul>
<li>Security: Added a secure AJAX endpoint with nonce and capability checks for dismissing admin notices.</li>
<li>Improvement: Modernized admin script and style loading to improve performance and adhere to WordPress best practices.</li>
<li>Improvement: Redesigned the the admin pages the petition settings page for a cleaner and more consistent user interface.</li>
<li>Improvement: The GDPR (Privacy Policy) setting is now mandatory when enabled.</li>
<li>Bug fix: Corrected an issue in an AJAX handler that could prevent petition emails from being sent correctly.</li>
<li>Bug fix: Prevented a potential PHP warning by ensuring the petition message is always a string.</li>
<li>Improvement: updated “tested up to” to WP version 6.8.3</li>
</ul>
<h3>4.6.0</h3>
<ul>
<li>Security: Hardened the plugin by adding comprehensive data sanitization and output escaping across all forms, AJAX handlers, and admin pages to prevent XSS and other vulnerabilities.</li>
<li>Security: Replaced direct use of <code>$_POST</code>, <code>$_GET</code>, and <code>$_REQUEST</code> variables with sanitized and validated data.</li>
<li>Security: Ensured all URLs generated by the plugin are properly escaped using <code>esc_url</code>.</li>
<li>Refactor: Completely overhauled the <code>[emailpetition]</code> shortcode rendering. The form HTML is now loaded from a separate template file ( <code>includes/email-petition-form-template.php</code>), improving code organization and making customization easier.</li>
<li>Refactor: Consolidated all mailing list integration logic (ActiveCampaign, MailChimp, etc.) into a single, cleaner function call.</li>
<li>Refactor: Improved custom field rendering by creating a dedicated helper function to reduce code duplication.</li>
<li>Refactor: Updated AJAX handlers to securely process and validate all incoming data.</li>
<li>Refactor: Switched to using WordPress best practices, such as <code>has_shortcode()</code> for content checking and <code>admin_url()</code> for creating admin links.</li>
<li>Tweak: Improved pagination logic to be more robust and prevent potential errors.</li>
</ul>
<h3>4.5.2</h3>
<ul>
<li>improvement: updated “tested up to” to WP version 6.8</li>
</ul>
<h3>4.5.1</h3>
<ul>
<li>bug fix: CSV export was throwing an error – thanks Vegard B.</li>
<li>improvement: updates to Swedish translations – thanks Magnus</li>
<li>improvement: updated “test to” to WordPress 6.8</li>
</ul>
<h3>4.5.0</h3>
<ul>
<li>improvement: further refined bug fixed in 4.4.0 – thanks Darius S. @ patchstack.com</li>
</ul>
<h3>4.4.3</h3>
<ul>
<li>improvement: updated old changelog link at end of current changelog</li>
</ul>
<h3>4.4.2</h3>
<ul>
<li>improvement: updated “Tested up to” to 6.7</li>
</ul>
<h3>4.4.1</h3>
<ul>
<li>bug fix: Export to CSV not working – thanks Vincent R & Shawn D</li>
</ul>
<h3>4.4.0</h3>
<ul>
<li>bug fix: fixed XSS vulnerability in specially crafted shortcode – thanks Darius S. @ patchstack.com</li>
</ul>
<h3>4.3.6</h3>
<ul>
<li>bug fix: wonky CSS setting in basic theme – thanks Jordan.</li>
</ul>
<h3>4.3.5.2</h3>
<ul>
<li>improvement: updated “tested to” to version 6.6</li>
</ul>
<h3>4.3.5.1</h3>
<ul>
<li>improvement: changed CSV max_execution_time from 180 to 300 seconds and moved it so it is only applied if script is actually run.  Also reset it to system default at end of script – thanks @gideonlupine</li>
</ul>
<h3>4.3.4</h3>
<ul>
<li>improvement: updated compatibility to WordPress 6.5</li>
</ul>
<h3>4.3.3.1</h3>
<ul>
<li>bug fix: debug code removed</li>
<li>bug fix: new social icons missing in free version</li>
<li>bug fix: in some circumstances an error was thrown in settings page – thanks Heiko</li>
</ul>
<h3>4.3.3</h3>
<ul>
<li>bug fix: error being thrown by field that can’t be edited in free version – thanks Giuseppe</li>
<li>bug fix: somehow above error wasn’t fixed in 4.3.2 – thanks Mayda</li>
</ul>
<h3>4.3.1</h3>
<ul>
<li>improvement: updated social icons in all style sheets</li>
</ul>
<h3>4.3.0</h3>
<ul>
<li>improvement: changed “twitter” to “X” – thanks Jos</li>
<li>improvement: removed some superfluous code</li>
<li>improvement: added Serbian language</li>
</ul>
<h3>4.2.6</h3>
<ul>
<li>bug fix: no error if privacy policy box not checked – thanks Mika</li>
<li>improvement: SpeakOut! now has its own domain SpeakOutPetitions.com</li>
</ul>
<h3>4.2.3</h3>
<ul>
<li>bug fix: In certain languages if privacy was enabled to show only the first letter of the surname, it would display a <code>?</code> instead – thanks Niklas</li>
<li>bug fix: signature list wouldn’t display if petition ID was greater than one.  This was implemented to limit free users, but it has unintended consequences for legacy users with multiple petitions.  Thanks Jim for letting me poke around.</li>
</ul>
<h3>4.2.2</h3>
<ul>
<li>improvement: updated “tested to” to 6.3</li>
</ul>
<h3>4.2.1</h3>
<ul>
<li>bug fix: multiple email addresses in Target Email or CC Email fields would be mashed together – thanks James and someone else who reported this</li>
</ul>
<h3>4.2.0</h3>
<ul>
<li>bug fix: custom field 6 location wasn’t being saved</li>
<li>bug fix: in admin signature list, “anonymous” icon was showing HTML instead of being superscript</li>
<li>improvement: added several webhooks – see https://speakoutpetitions.com/webhooks. Thanks for the idea Ben & Nick</li>
<li>improvement: added email share icon to Pro version – thanks to whoever suggested it.</li>
<li>improvement: displaying emails in the public signature list is now optional – with a warning that it might not be a wise idea</li>
<li>improvement: translation updates</li>
</ul>
<h3>4.1.3.1</h3>
<ul>
<li>bug fix: Somehow a stray character found its way into the code which was breaking petitions. – thanks Meagan</li>
</ul>
<h3>4.1.2</h3>
<ul>
<li>bug fix: database creation error for new installs</li>
<li>bug fix: if message was editable, formating was lost when sent to target (Pro only) – thanks Linda</li>
<li>bug fix: language wasn’t bein passed via URL in confirmation emails</li>
<li>improvement: eliminated php warning “ob_end_flush(): failed to send buffer of zlib output compression”</li>
<li>improvement: added note to when “Do not send email (only collect signatures)” is checked</li>
</ul>
<h3>4.1.1</h3>
<ul>
<li>bug fix: if the <em>petitionmessage</em> shortcode was used, any Markdown in the message wasn’t being displayed.  Thanks Michael.</li>
<li>bug fix: if email confirmation was enabled, the numbering in the public signature list reflected the total number of signatures, not just the confirmed signtures.  Thanks Rene & Martin</li>
<li>bug fix: if email confirmation was enabled and public signatures spanned more than one page, scrolling didn’t work as expected – thanks Rene</li>
<li>bug fix: on one layout of the public signature list, the word <em>anonymous</em> wasn’t translated – thanks Myriam-Zaa</li>
<li>bug fix: increased size of honorifics field in database – thanks Glen C.</li>
<li>bug fix: following some actions in the admin signature list it wasn’t showing the signature count</li>
<li>improvement: new installs will now use the utf8mb4_general_ci character set for database text fields, instead of just utf8 – down the track I will change the character set for existing installs</li>
<li>improvement: database creation now makes fields NULL instead of NOT NULL to allow for not collecting some data – down the track I will change all fields to NULL in existing installs</li>
</ul>
<h3>4.1.0</h3>
<ul>
<li>bug fix: Confirmation emails weren’t being sent if Email From field wasn’t set up properly, which was impossible.  Thanks Thomas and Rene</li>
<li>bug fix: non-existant parameter being passed to function</li>
<li>improvement: updated the contextual help – first time ever :o)</li>
<li>improvement: clarified wording of “display signature count” and where it refers to.</li>
<li>improvement: database updates so free version is ready to upgrade to Pro</li>
</ul>
<h3>4.0.10</h3>
<ul>
<li>improvement: changed a page title – thanks Debbie P</li>
<li>bug fix: some required fields were not showing red border – thanks Debbie P</li>
<li>bug fix: redirect after signing not working – thanks Debbie P</li>
</ul>
<h3>4.0.9</h3>
<ul>
<li>bug fix: when clicking <em>next</em> in signature list it was displaying html – thanks Dan @tahninial</li>
</ul>
<h3>4.0.8</h3>
<ul>
<li>bug fix: slashes added to any apostrophes in email subject or greeting</li>
<li>bug fix: missing default value in free version</li>
</ul>
<h3>4.0.7</h3>
<ul>
<li>bug fix: missing character would cause error in certain circumstances – thanks heiko</li>
</ul>
<h3>4.0.6.1</h3>
<ul>
<li>bug fix: if WordPress was installed in a subfolder, some administrator links may not have worked.  Thanks Calvin</li>
</ul>
<h3>4.0.6</h3>
<ul>
<li>bug fix: petition message kept adding slashes in editor when saved.  Thanks Calvin</li>
<li>improvement: removed <em>%%Your Signature%%</em> from the petition message displayed on your site.  It was causing confusion.  Thanks Razvan</li>
<li>improvement: minor typo fixed</li>
<li>improvement: Dutch language imrovements – thanks Michiel</li>
</ul>
<h3>4.0.5</h3>
<ul>
<li>bug fix: petition message losing formatting – thanks @dcbuffalo</li>
<li>improvement: better data sanitization in signature list</li>
</ul>
<h3>4.0.4.6</h3>
<ul>
<li>bug fix: html being displayed in admin signature list</li>
<li>bug fix: file was being included twice</li>
<li>bug fix: reconfirming selected signatures wasn’t working</li>
</ul>
<h3>4.0.4.5</h3>
<ul>
<li>bug fix: settings not saving due to incorrect input sanitize function</li>
<li>improvement: German language update – thanks Mario</li>
</ul>
<h3>4.0.4.4</h3>
<p>bug fix: in some circumstances an error was thrown in settings page – thanks Heiko</p>
<h3>4.0.4.2</h3>
<ul>
<li>Policy compliance: Version 3 of SpeakOut! included a method of upgrading that turned out to be a WordPress plugin policy breach (4 months later!) and some potential security issues (after 10+ years!).  This version remedies that and introduces a more cumbersome (for users), but compliant method of upgrading.</li>
<li>bug fix: various fixes of things found while creating V4</li>
<li>improvement: removed support for importing the original speakup plugin.  After 10 years, it’s time.</li>
</ul>
<p><a href="https://speakoutpetitions.com/speakout-free-changelog/" title="SpeakOut! old Changelog" rel="nofollow ugc">Earlier Changelog</a></p>
<h3>Localizations</h3>
<ul>
<li>Albanian <strong>sq_AL</strong> Incomplete</li>
<li>Arabic <strong>ar_AR</strong></li>
<li>Arabic <strong>ar</strong> (Faisal Kadri)</li>
<li>Catalan <strong>ca</strong>  (Alberto Canals)</li>
<li>Czech <strong>cs_CZ</strong> (Petr Å tepÃ¡n, Michal HradeckÃ½)</li>
<li>Danish <strong>da_DK</strong> (A. L.)</li>
<li>Dutch <strong>nl_NL</strong> (Kris Zanders, Petronella van Leusden)</li>
<li>Finnish <strong>fi_FI</strong> </li>
<li>French <strong>fr_FR</strong></li>
<li>German <strong>de_DE</strong> (Hannes Heller, Armin Vasilico, Andreas Kumlehn, Frank Jermann)</li>
<li>Hebrew <strong>he_IL</strong> (Oren L)</li>
<li>Korean <strong>ko_KO</strong> (Paul Lawley-Jones)</li>
<li>Icelandic <strong>is_IS</strong> (Hildur Sif Thorarensen)</li>
<li>Italian <strong>it_IT</strong> (<a href="https://wordpress.org/support/profile/macitaly" rel="ugc">MacItaly</a>, Davide Granti, Simone Apollo)</li>
<li>Norwegian <strong>nb_NO</strong> (Howard Gittela)</li>
<li>Polish <strong>pl_PL</strong> (Damian Dzieduch)</li>
<li>Portuguese (Brazil) <strong>pt_BR</strong> (Tel Amiel)</li>
<li>Romanian <strong>ro_RO</strong> (<a href="http://webhostinggeeks.com" rel="nofollow ugc">Web Hosting Geeks</a>)</li>
<li>Russian <strong>ru_RU</strong> (<a href="te-st.ru" rel="nofollow ugc">Teplitsa</a>)</li>
<li>Serbian <strong>sr_RS</strong> (Mikhailo Matovic)</li>
<li>Slovak <strong>sk_SK</strong> (@Beata)</li>
<li>Slovenian <strong>sl_SI</strong> (<a href="http://ma-seo.com" rel="nofollow ugc">MA-SEO</a>)</li>
<li>Spanish <strong>es_ES</strong></li>
<li>Swedish <strong>sv_SE</strong> (Susanne Nyman FurugÃ¥rd @sunyfu)</li>
</ul>
<p>If you would like to request or contribute a specific translation not listed above, visit the <a href="http://speakoutpetitions.com/" rel="nofollow ugc">SpeakOut! Email Petitions website</a> and use the contact form.</p>
<h3>Emailpetition Shortcode Attributes</h3>
<p>The following attributes may be applied when using the ‘[emailpetition]’ shortcode</p>
<h4>id</h4>
<p>The ID number of your petition (required). To display a basic petition, use this format:<br />
‘[emailpetition id=”1″]’</p>
<h4>width</h4>
<p>This sets the width of the wrapper “</p>
<p><</p>
<p>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.</p>
<p>To set the petition from to display at 100% of it’s container, use:<br />
‘[emailpetition id=”1″ width=”100%”]’</p>
<p>A petition set to display at 500 pixels wide can be achieved using:<br />
‘[emailpetition id=”1″ width=”500px”]’</p>
<h4>height</h4>
<p>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.</p>
<p>A few notes on using percentages:<br />
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 ‘</p>
<p><</p>
<p>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.</p>
<p>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.</p>
<p>Examples:<br />
‘[emailpetition id=”1″ height=”500px”]’</p>
<p>‘[emailpetition id=”1″ height=”100%”]’</p>
<h4>progresswidth</h4>
<p>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.</p>
<p>To display the progress bar at 300 pixels wide, use:</p>
<p>‘[emailpetition id=”1″ progresswidth=”300″]’</p>
<h4>class</h4>
<p>Adds an arbitrary class name to the wrapper ‘</p>
<p><</p>
<p>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.</p>
<p>Examples:</p>
<p>‘[emailpetition id=”1″ class=”alignright”]’</p>
<p>‘[emailpetition id=”1″ class=”style1 style2″]’</p>
<h3>Signaturelist Shortcode Attributes</h3>
<h4>id</h4>
<p>The ID number of your petition (required). To display a basic signature list, use this format:</p>
<p>‘[signaturelist id=”1″]’</p>
<h4>rows</h4>
<p>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:</p>
<p>‘[signaturelist id=”1″ rows=”10″]’</p>
<h4>dateformat</h4>
<p>Format of values in the date column. Use any of the standard <a href="http://php.net/manual/en/function.date.php" rel="nofollow ugc">PHP date formating characters</a>. Default is ‘M d, Y’. A date such as “Sunday October 14, 2012 @ 9:42 am” can be displayed using:</p>
<p>‘[signaturelist id=”1″ dateformat=”l F d, Y @ g:i a”]’</p>
<h4>prevbuttontext</h4>
<p>The text that displays in the previous signatures pagination button. Default is <.</p>
<h4>nextbuttontext</h4>
<p>The text that displays in the next signatures pagination button. Default is >.</p>
<h3>signaturecount Shortcode</h3>
<p>Display the number (as text) of signatures collected for a given petition:</p>
<h4>id</h4>
<p>The ID number of your petition (required).</p>
<p>‘[signaturecount id=”3″]’</p>
<h3>signaturegoal Shortcode</h3>
<p>Display the number (as text) of goal for a given petition:</p>
<h4>id</h4>
<p>The ID number of your petition (required).</p>
<p>‘[signaturegoal id=”3″]’</p>


SpeakOut! Email Petitions

Absolutely amazing as a free plugin. The environmental group I built a site for needed public email petitions, and it fills the bill. They moved their main site to SquareSpace but keep a separate WP site just to retain SpeakOut's functionality.

Only viable option, and it's quite good

SpeakOut! Email Petitions makes it easy to add petitions to your website and rally your community to Speak Out about a cause by using direct action.

Members Category vs SpeakOut! Email Petitions