Andrei

atanasprchev

Elena

<p>Control what menu items your site’s visitors see, with visibility rules. Here are a few examples:</p>
<ul>
<li>Display a menu item only if <code>User is logged in</code></li>
<li>Hide menus if <code>Device is mobile</code></li>
<li>Display menus only for <code>Admins and Editors</code></li>
<li>Hide Login or Register links for <code>Logged in Users</code></li>
<li>Display menus for <code>Users from US or UK</code></li>
<li>Display menus only for <code>Customers with active membership</code></li>
<li>Display menus for visitors browsing with <code>Language English or Spanish</code></li>
</ul>
<p>After the plugin is enabled, each menu item will have a new option “Change menu item visibility” which will enable the selection of visibility rules.</p>
<p>Check the examples in screenshots or try it here <span aria-hidden="true" class="wp-exclude-emoji">→</span> <a href="https://demos.layered.store" rel="nofollow ugc">demos.layered.store</a></p>
<h3>Features</h3>
<ul>
<li>Basic set of visibility rules
<ul>
<li>User state <code>User is logged in</code></li>
<li>User roles <code>Admin</code> <code>Editor</code> <code>Author</code> etc</li>
<li>Page type <code>Front page</code> <code>Single page</code> <code>Single post</code></li>
<li>Is Archive page (year, category, search results, etc)</li>
<li>Visitor device <code>Is Mobile</code></li>
</ul>
</li>
<li>Advanced visibility rules – requires <a href="https://layered.store/plugins/more-visibility-rules" rel="nofollow ugc">More Visibility Rules Add-on</a>
<ul>
<li>Visitor location – detect visitor’s Country</li>
<li>Visitor language – detect visitor’s selected Language</li>
<li>WooCommerce Subscriptions – Display menus for users with active subscription</li>
<li>WooCommerce Memberships – Display menus for customers with active membership plans</li>
<li>Groups – Detect if users are in specific groups</li>
<li>WishList Member – Detect the users’ membership level</li>
<li>Restrict Content Pro – Detect the users’ subscription level</li>
</ul>
</li>
<li>Multiple rules – mix multiple rules for a menu item visibility
<ul>
<li>show if <code>User is logged in</code> AND <code>Device is mobile</code></li>
<li>show if <code>User is Admin</code> AND <code>Is front page</code></li>
</ul>
</li>
<li>Support for <a href="https://wordpress.org/plugins/if-menu/#how%20can%20i%20add%20a%20custom%20visibility%20rule%20for%20menu%20items%3F" rel="ugc">adding your custom rules</a></li>
</ul>


If Menu – Visibility control for Menus

Display tailored menu items to each visitor with visibility rules

codefarma

<p>Automation allows you to build new features on the fly and automate plugins using simple “rules”.</p>
<p>Use “rules” to assign what happens on your site when certain events occur. An individual rule consists of an event, some conditions to check, and one or more actions to take. For example:</p>
<p><strong>Rule 1.</strong></p>
<blockquote>
<p><code>Event:</code> <strong>When a user logs in…</strong><br />
  <code>Action:</code> <strong>Increment a login count for the user.</strong></p>
</blockquote>
<p><strong>Rule 2.</strong></p>
<blockquote>
<p><code>Event:</code> <strong>When a user logs in…</strong><br />
  <code>Condition:</code> <strong>If their login counter has reached a certain threshold…</strong><br />
  <code>Action:</code> <strong>Promote the user to a new member role.</strong></p>
</blockquote>
<p>Multiple rules can work in coordination with each other to create workflows and custom features.</p>
<p>A rule is the building block for creating automations, and automations are a path to create new custom site features by connecting various “automation ready” plugins and their behaviors in new ways.</p>
<p>The possibilities of what you can automate is only limited by your imagination (or the number of “automation ready” plugins you have installed on your site). If you want to automate features of a plugin that is not yet automation ready, that’s not a problem because an expansion pack can easily be created to make it automation ready.</p>
<h3>Automation Bundles</h3>
<p>Multiple “rules” can be grouped together into “automation bundles”, which is a convenient way to package and share your creations with other site owners. These “automation bundles” allow anybody to create customized behaviors between automation ready plugins, and distribute those in a way that allow others to use them with minimal configuration.</p>
<h3></h3>
<h3>Fixed</h3>
<ul>
<li>Fixed some PHP notices being generated</li>
<li>Fixed problem where changing the action/condition type wipes out any edits to the description</li>
<li>Fixed issue with data selectors not being able to insert tokens into wp editors or codemirror editors</li>
</ul>
<h3>Added</h3>
<ul>
<li>Added new capabilities to the “Output To HTML” action which allows it to output to a different hook, and also<br />
allows the use of replacement tokens and shortcodes.</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Changed branding to OtterMate</li>
</ul>
<p>1.3.1</p>
<h3></h3>
<h3>Fixed</h3>
<ul>
<li>Fixed a bug when using a array key value in a token for an event argument</li>
<li>Fixed a bug where selecting a deep token from the data browser didn’t show the token</li>
<li>Fixed the details that show in the hover title of data browser data points</li>
<li>Fixed a bug causing arrays with non loadable objects to not have their class mappings appear in the data browser</li>
</ul>
<p>1.3.0</p>
<h3></h3>
<h3>Added</h3>
<ul>
<li>Added support for new “Specialization” site rules that have configurable but pre-determined behavior</li>
<li>Added core specialization for conditional post access rules</li>
<li>Added new dashboard to manage site rules</li>
<li>Added new ability to select a data point when creating conditions to filter condition choices</li>
<li>Rules are now linked on the summary screen after importing automations to allow access to immediately edit them</li>
<li>All new token pieces have been added for array values to derive sums, splices, unique values, and perform sorts</li>
<li>Condition configuration has been changed from two step creation to single step using ajax forms</li>
<li>Added data browser access to WP_Query tokens</li>
<li>Added ability to use custom actions as WordPress API endpoints</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Rules Engine admin interface has been renamed to Rules Studio</li>
<li>A validation error now occurs when attempting to create duplicate custom event hooks</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Fixed issue with the send mail action causing it to not log to the email log</li>
</ul>
<p>1.2.3</p>
<h3></h3>
<h3>Fixed</h3>
<ul>
<li>Updated MWP Framework to 1.2.11 for compat with latest Woo</li>
</ul>
<p>1.1.4</p>
<h3></h3>
<h3>Added</h3>
<ul>
<li>Date/Time config widget presets</li>
<li>Taxonomy config widget presets</li>
<li>A creator field can now be specified for rule bundles</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Token browser launch button re-styled</li>
<li>Performance improvements via new table indexes</li>
<li>Email action now supports token replacements</li>
<li>Recurring action schedule is now visible on scheduled actions table</li>
<li>Removed ‘before_setup_theme’ rule event since it is unhookable by rules</li>
<li>Rules Engine link appears in network admin menu for multisite installs</li>
<li>Downloaded rules files now have a suffix that matches the type of rule package</li>
<li>Flushing the system logs table now just truncates the table instead of iterating and deleting</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Bug causing rule conditions not to be re-organizable</li>
<li>Bug getting bundle url with custom parameters via code</li>
<li>Bug causing condition ‘compare’ mode not to save</li>
<li>Bug causing table on rules debug tabs to not be pageable</li>
<li>Bug with line endings being present on arrays entered through input widgets</li>
<li>Bug with null rule_parent_id causing rules to not be visible in tables</li>
<li>Bug causing post meta crud events to not be available for use by rules</li>
</ul>
<p>1.1.3</p>
<h3></h3>
<h3>Added</h3>
<ul>
<li>Custom actions can now be scheduled manually</li>
<li>Token browser now shows mapped array keys for event args</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Removed manual config form option for custom action arguments that do not have a config widget</li>
<li>Widened the hook priority support for rule deployments</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Auto detect provider for ecas registered by plugins that are network enabled</li>
</ul>
<p>1.1.2</p>
<h3></h3>
<h3>Added</h3>
<ul>
<li>Array value search condition now has setting for case insensitivity</li>
<li>New ‘checkbox’ config preset widget</li>
<li>Any class that extends <code>MWP\Framework\Pattern\ActiveRecord</code> can now automagically register a full set of ECA’s with rules via static method <code>registerRulesECAs()</code></li>
<li>Token selector now available on the action scheduling unique key form input</li>
<li>Added support for storing references to known objects in the class map for later loading</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Event argument selection is now always available in condition/action config, even if no event args can be matched to 2 levels</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Fixed scheduled action controller not conforming to proper database schema</li>
<li>Fixed custom log entries not showing after editing default sort order on log</li>
<li>Fixed non-working token replacement on action scheduling unique key</li>
<li>Fixed non-working scheduled action unique key management</li>
<li>Fixed scheduled actions not working when operating on stored objects</li>
<li>Fixed custom filters not showing on custom events page</li>
</ul>
<p>1.1.1</p>
<h3></h3>
<h3>Changed</h3>
<ul>
<li>Improved the capabilities of the string comparision core condition to handle checking against arrays</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Fixed broken show/hide form rows on post/comment update action config forms</li>
</ul>
<p>1.1.0</p>
<h3></h3>
<h3>Added</h3>
<ul>
<li>Token browser added. Event argument selection and token replacements can now be browsed using a gui.</li>
<li>Custom logs and custom log entries are now accessible through the token browser.</li>
<li>Custom logs can now be customized to choose default sorting, alternate sorting, and searching columns.</li>
<li>Log entries count now displays on the dashboard logs tab</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Changed to work with MWP Framework 2.1.x</li>
</ul>
<p>1.0.5</p>
<h3></h3>
<h3>Added</h3>
<ul>
<li>Full exception handling for PHP7</li>
<li>Token mappings for current site properties</li>
<li>Added a link to get to the system log in the admin menu</li>
</ul>
<h3>Changed</h3>
<ul>
<li>The redirect rules action is now safeguarded against redirecting when in the admin interface</li>
<li>Downloads of rules now auto name the file according to the item being downloaded</li>
<li>The view template for custom logs now display their field name instead of the database column name</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Error caused when using the token evaluator function in custom php actions/conditions</li>
<li>Base compare setting for conditions was not saving to the rule</li>
</ul>
<p>1.0.4</p>
<h3></h3>
<h3>Added</h3>
<ul>
<li>New field for custom events to categorize them</li>
<li>Providers of ECA’s are now tracked in rules exports</li>
<li>Custom events and custom actions now have separate management screens</li>
<li>Custom actions can have rules assigned to them which comprise their core functionality</li>
<li>Added multisite support which moves rules administration to the network admin and allows rules to target specific sites</li>
</ul>
<p>1.0.3</p>
<h3></h3>
<h3>Added</h3>
<ul>
<li>Bundles can now have a menu item added to the WP Settings Menu</li>
<li>Added ability to specify attachments in the email action</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Removed foreign key references from exported rule data</li>
<li>Adjusted verbage for exporting rules from ‘Export …’ to ‘Download …’</li>
<li>Removed the download option from the dashboard bundle panel</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Corrected active record class map generation output</li>
</ul>
<p>1.0.2</p>
<h3></h3>
<h3>Added</h3>
<ul>
<li>Improvements to user interface</li>
<li>Menu item for custom logs to manage fields</li>
<li>Menu item for custom logs to flush entries</li>
<li>Started tracking the rules_apps table for future use</li>
<li>Added an extension to the ActiveRecord class to add the class to the rules map <code>addToRulesMap()</code></li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Fixed broken uninstall routine</li>
<li>Fixed various php notices</li>
<li>Fixed database errors caused by non-present tables on initial install</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Removed unused dependency tracking code</li>
<li>Removed search box from rules controller</li>
</ul>
<p>1.0.1</p>
<h3></h3>
<h3>Added</h3>
<ul>
<li>Event: Admin Initialized</li>
<li>Event: Admin Header</li>
<li>Event: Admin Footer</li>
<li>Event: Login Attempt Failed</li>
<li>Date/time now displays by default on log entries table</li>
<li>Added internal api methods to get specific arguments from hooks, logs, and bundles</li>
<li>Added a <code>$token_value</code> variable which contains a function that can be used to get token values inside rule configuration custom php code.</li>
<li>Added quick enable/disable labels to bundles, rules, conditions, and actions</li>
<li>Added custom log field visibility options</li>
<li>Added custom log retention maintenance settings</li>
</ul>
<h3>Changed</h3>
<ul>
<li>“Log entry created” events now recieve the log and entry as arguments</li>
<li>Added css styles to suppress notice and update messages on rules admin pages</li>
<li>String database column size increased from 255 to 1028</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Completed the incomplete ‘update filter value’ action</li>
</ul>
<p>1.0.0</p>
<h3></h3>
<ul>
<li>First official release</li>
</ul>


Automation Rules

We've been looking for a plugin like this for years on WordPress. Most other CMS platforms have some sort of 'rules' system but WordPress has been missing it. This plugin is super comprehensive, tons of features!

Game Changing!

Automation allows you to build new features on the fly and automate plugins using simple "rules".

If Menu – Visibility control for Menus vs Automation Rules