JetEngine Custom Visibility Conditions 1.1.2
JetEngine Custom Visibility Conditions, a WordPress plugin, extends the Dynamic Visibility module with two new rules—Post Status is and Is post by current user—allowing you to show or hide sections based on post status or the current author.
Description
JetEngine Custom Visibility Conditions is a JetEngine add-on for WordPress that extends the Dynamic Visibility module used with Elementor. It adds two extra rules so you can control whether sections, columns, or widgets appear on the page. Instead of relying only on basic display checks, you can tie layout visibility to content state and author context.
With “Post Status is,” you can show or hide elements based on whether a post is in a specific status (such as draft or published). With “Is post by current user,” you can tailor visibility to the current author, supporting cleaner, more relevant pages for each person viewing the content.
Main Features
- Adds custom rules to JetEngine Dynamic Visibility — Extends the Dynamic Visibility module inside the JetEngine Elementor workflow.
- “Post Status is” condition — Shows or hides elements depending on the target post’s status.
- Visibility controls for Elementor elements — Applies to sections, columns, and widgets built with JetEngine.
- “Is post by current user” condition — Makes elements visible or invisible based on whether the current viewer is the post author.
- Author-aware layout behavior — Enables different UI states for owners versus other visitors.
- Works with post-based templates — Fits common use cases in Elementor templates powered by JetEngine.
- Improves conditional page structure — Lets you design cleaner layouts by showing only relevant content blocks.
- Supports content lifecycle display — Helps you present or conceal components according to the post’s publishing workflow.
Benefits
- More relevant pages — Display the right sections based on post status and author identity.
- Better user experience — Reduce clutter by hiding empty or inappropriate blocks.
- Higher conversion signals — Focus calls-to-action on the correct audience and content state.
- Cleaner template logic — Keep visibility rules centralized in JetEngine instead of manual workarounds.
- Consistency across templates — Apply the same visibility conditions throughout Elementor layouts.
Who is it suitable for?
- WooCommerce stores using JetEngine/Elementor to present post-driven content
- Blogs and publishers needing status-based layout control (e.g., draft vs published)
- Web agencies building author-aware client templates with JetEngine
- Content platforms with multi-author workflows and preview-style UI
- Community or membership sites where only authors should see specific elements