Adam Harley (Kawauso)

<p>A quick adaptation of the theme restriction code for plugins. Can only restrict on a site-wide basis, though it will only affect those sites on which it’s activated. Does not restrict super admins. Plugins <strong>must</strong> be active on the main site to be controlled by this plugin (this is an issue with WordPress’ plugin structure).</p>
<p>See also: <a href="https://wordpress.org/extend/plugins/restrict-multisite-widgets/" rel="ugc">Restrict Multisite Widgets</a></p>


Restrict Multisite Plugins

Allows network admins to restrict which plugins are available on sites, similar to themes.

Vlado Grcic

<p>Page Restrict for WooCommerce is a plugin that sells access to pages, posts and custom post types through WooCommerce. It’s been built with Gutenberg in mind as well as the classic editor. You can restrict pages in two ways. Restrict an entire page or restrict sections on the page. In case you want to restrict sections on the page you can use blocks for the Gutenberg editor and using shortcodes for the classic or similar editors. If you want to restrict entire pages you can use enable the sidebar in the More tools & options in the Gutenberg editor or use the page metabox in the classic editor. You can also restrict all of your pages in one place in the Pages plugin menu.</p>
<h4>Requirements</h4>
<ul>
<li>WooCommerce to be installed and active</li>
<li>Guest checkout needs to be disabled</li>
<li>PHP 7.0.25+. </li>
</ul>
<h4>Features</h4>
<ul>
<li>Restrict content from pages, posts and custom post types based on if they have purchased a specific WooCommerce product</li>
<li>Restrict entire page or just sections of it</li>
<li>Use one or multiple products to restrict it and choose whether you want to require the user to buy all of them to access or at least one of the products that restrict. </li>
<li>Restrict by time – Set a time limit for the user after which they won’t be able to see the content.</li>
<li>Restrict by views – Set a view count for the user after which they won’t be able to see the content ( currently only if you want to restrict entire pages ).</li>
<li>Use other pages or posts for specific pages as Restricted Messages</li>
<li>Use default pages or posts for all restricted pages as Restricted Messages</li>
<li>Redirect to the chosen page instead of just showing the other pages content</li>
<li>Built for use with the latest Gutenberg editor as well as the classic one</li>
<li>Use either Gutenberg blocks or shortcodes to restrict sections on a page or post</li>
<li>Plugin menu page to handle all pages you need to restrict in one place called Pages</li>
<li>Plugin menu page to get an overview of all users that bought a product required to access an restricted page which either is still valid or already expired called User Overview.</li>
<li>Similar feature to User Overview for the frontend for each user to have an overview of their pages where they bought products in order to access them.</li>
<li>A Quick Start menu page to get you started on using this plugin</li>
</ul>
<h4>Blocks</h4>
<p><strong>page-restrict-wc/restrict-section</strong><br />
Section Restrict for WooCommerce – Restricts a section on the page using this grouping element.</p>
<p><strong>page-restrict-wc/restricted-pages-list</strong><br />
Restricted Pages List – Shows a table of restricted pages for the current user which have had bought products for.</p>
<h4>Shortcodes</h4>
<p>[prwc_is_purchased products=”1,2″ days=”25″ hours=”2″ minutes=”45″ seconds=”15″ inverse=”false” defRestrictMessage=”Restrict Message” notAllProductsRequired=”false” defaultPageNotBoughtSections=”4″ defaultPageNotLoggedSections=”5″]</p>
<ul>
<li>Restricts the content using the chosen options. </li>
<li>products – choose which products to restrict with. Add product IDs separated by a comma.</li>
<li>Timeout options for this are days, hours, minutes, seconds.</li>
<li>inverse – using the inverse option you can choose inverse=”false” to hide the content in order for the user to not see it. Choose inverse=”true” for the user to see it in order to show them instructions on what to do to access the desired content you chose using inverse=”false”</li>
<li>defRestrictMessage – is the message you want to show if the user didn’t buy the product.</li>
<li>notAllProductsRequired – set to true if the user doesn’t need to buy all products.</li>
<li>defaultPageNotBoughtSections – you can choose a page to show instead of a message like in defRestrictMessage.</li>
<li>defaultPageNotLoggedSections – you can choose a page to show if the user isn’t logged in.</li>
</ul>
<p>[prwc_restricted_pages_list table=”time” disable_table_class=”false”]</p>
<ul>
<li>Shows a table of restricted pages for the current user which have had bought products for.</li>
<li>Using the table attribute you can choose which table of restricted page you will show. It can show pages that are restricted either by time or view count.</li>
<li>Using disable_table_class attribute you can choose whether to kepp or not to keep the default plugin style for the tables.</li>
<li>You can show restricted pages that timeout either by time or view. </li>
</ul>
<h4>Coming soon</h4>
<ul>
<li>Restrict categories</li>
<li>Restrict authors</li>
</ul>


Page Restrict for WooCommerce

Restrict access to your WordPress pages using WooCommerce products.

Restrict Multisite Plugins vs Page Restrict for WooCommerce