Dynamic Visibility - Triggers - User & Role
When you want to set advanced conditions in Elementor you can choose different triggers that can change the visibility of the element in many situations.
WARNING: you can actually set only one trigger at once. You cannot add them up together. If you set many triggers, they will work when at least one of them is checked.
User & Role
To make it easier, Visitors (non logged users) will be considered as a Role.
- a Private content available only for registered users (like Membership, with multi level of Roles);
- some particular Notes for Administrator only;
- a Registration form or CTA visible by non logged users.
If multiple users need to separate them by a comma (1,pippo,23,firstname.lastname@example.org,17).
- show specific content for some users without grouping them with a role;
- show a new content only for the Web designer while working on it.
Show content only to current Post Author
Write the user capability string.
It works only for logged in users, for visitors the result is always false.
The second step is to select what kind of value is expected:
- Empty, like null or false;
- not empty, valued with any value;
- Less than;
- Greater than;
- Not Contain;
- In Array, check if the user field is in an array (also from a comma separated values string);
- Equal to, exactly a defined value;
- Not Equal to, different from a defined value.
- show an alert for each User that shows his phone number, to edit his Profile and add it.
User differ from a unique IP, so you can specify it and limit for single connections.
- your agency has a Static IP so you can show specific sections only for Web designer connected inside your structure;
- your client has a Static IP on his office, so you can preview to him to get confirmation about your new contents before releasing them as public.
If multiple sites write them one for lines.
- show a specific message to all visitors that come from Facebook
Select a specific category of devices defined by its size:
- Desktop and TV
- Mobile and Tablet
Contents will be removed from code, so if something will be visible on Mobile it will not be visible on Desktop.
Will be used native WordPress detection:
This detection is limited, but in the future release will be expanded with third-party libraries.
- create a custom interface for Mobile device and another for Desktop in the same template maintaining a lightweight code (usually you simple hide the unwanted by CSS but the content is duplicated in the HTML code)
- limit some advanced function only for Desktop user
- some technology not working well on specific Browser (like Flash on Safari or CSS FlexBox on IE), so is better remove it