RCP Elementor Dynamic Tags
Add RCP Dynamic Tag to Elementor
by Chris Bibby · github.com/cmbibby/rcp-elementor-dynamic-tags · website
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/cmbibby/rcp-elementor-dynamic-tags/archive/refs/heads/master.zipReadme
=== Rcp Elementor Dynamic Tags === Contributors: cmbibby Tags: restrict content pro, elementor, dynamic tags Requires at least: 4.5 Tested up to: 5.4.2 Stable tag: 1.0.0 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html
Adds a Dynamic Tag to Elementor Pro for Restrict Content Pro to return whether the current user has an active membership or not.
== Description ==
This plugin creates a dynamic tag for Elementor Pro that returns whether or not the user has an active membership or not. Used in conjunction with the Dynamic Conditions https://wordpress.org/plugins/dynamicconditions/ plugin you can easily use RCP conditional logic in Elementor Pro.
== Installation ==
You need
Requires Elementor Pro and Restrict Content Pro to work
- Unzip
rcp-elementor-dynamic-tags.zipto the/wp-content/plugins/directory - Activate the plugin through the 'Plugins' menu in WordPress
== Screenshots ==
- This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets
directory take precedence. For example,
/assets/screenshot-1.pngwould win over/tags/4.3/screenshot-1.png(or jpg, jpeg, gif). - This is the second screen shot
== Changelog ==
= 1.0 =
- A change since the previous version.
- Another change.
= 0.5 =
- List versions from most recent at top to oldest at bottom.
== Upgrade Notice ==
= 1.0 = Upgrade notices describe the reason a user should upgrade. No more than 300 characters.
= 0.5 = This version fixes a security related bug. Upgrade immediately.
== Arbitrary section ==
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or "installation." Arbitrary sections will be shown below the built-in sections outlined above.
== A brief Markdown Example ==
Ordered list:
- Some feature
- Another feature
- Something else about the plugin
Unordered list:
- something
- something else
- third thing
Here's a link to WordPress and one to Markdown's Syntax Documentation. Titles are optional, naturally.
"Markdown is what the parser uses to process much of the readme file"
Markdown uses email style notation for blockquotes and I've been told:
Asterisks for emphasis. Double it up for strong.
<?php code(); // goes in backticks ?>