JetEngine plugin review and common issues

Blank field values in listing templates indicate a field name mismatch or a dynamic tag configuration issue. Open the listing template in Elementor and click each dynamic tag to verify: (1) the Dynamic Tag type is set to “JetEngine” → “Meta Data” (not a generic Elementor dynamic tag); (2) the Meta Key field contains the exact field name (slug) from JetEngine → Meta Fields — case-sensitive; (3) the listing’s source Post Type matches the Post Type where the fields are registered. If the template is used inside a JetEngine Listing Grid, verify the grid’s Post Type also matches.

Open the Query in JetEngine → Query Builder → [query name]. In the Edit Query panel, review all filters under “Meta Clauses” and “Taxonomy Clauses.” Verify: (1) meta filter field names match exactly the JetEngine field slugs or WordPress meta keys; (2) comparison operators are set correctly (equals, contains, greater than, etc.); (3) the query is saved and re-applied to the Listing Grid — after changing query parameters, go to the Listing Grid on the page and resave the widget. Use the “Preview Results” option in the Query Builder to see how many posts match the current filter configuration.

JetEngine relationships can be set to bidirectional in the relationship settings. Go to JetEngine → Relations → [relationship name] and check the “Build Relations Both Ways” option. When enabled, connecting a child post to a parent also registers the reverse relationship, visible from the parent post. If bidirectional is enabled but the reverse relationship is not appearing, flush WordPress object cache and reload the related post’s edit screen. Also ensure the relationship is of type “Many-to-Many” — one-to-one and one-to-many relationships have different bidirectional display logic.

Add a Map field to your custom post type in JetEngine → Meta Fields. In the listing item template, add a Dynamic Tag for the Map field to store coordinates. On the directory page, add a JetEngine Maps Listing widget — this widget takes the Listing Template and a Query Builder query as input and renders all matching posts as pins on a Google Map. Configure the Google Maps API key in JetEngine → Settings → Google Maps API. Clicking a map pin can reveal a popup with the listing template content or navigate to the post’s single page.

Go to JetEngine → Meta Fields for your post type and add a new field of type “Calculated.” In the formula field, enter a mathematical expression using other field names in double curly braces: {{price_per_night}} * {{nights_count}}. JetEngine evaluates this formula when displaying the field, returning the computed result. Calculated fields support basic arithmetic (+, -, *, /), PHP math functions (round(), ceil(), floor()), and comparisons. Display the calculated field in a Listing Template via a JetEngine Meta Data dynamic tag like any other field.

JetEngine is more than a custom fields replacement — it combines the data storage of ACF with the front-end display system that ACF requires a page builder or custom PHP to achieve. For Elementor-based sites building complex data-driven layouts, JetEngine often replaces ACF entirely because it provides dynamic display without additional tooling. For simple custom field storage without complex front-end display requirements, ACF remains simpler and more widely supported. The choice depends on whether front-end dynamic display in Elementor is a core site requirement.

JetEngine increasingly supports Gutenberg and the Bricks Builder alongside Elementor. The custom post types, taxonomies, and meta fields work independently of any page builder. However, the Listing Builder and Query Builder’s full dynamic display capabilities are most complete in Elementor. For Gutenberg-based sites, JetEngine provides Dynamic Blocks for displaying field data but lacks the visual sophistication of the Elementor Listing Builder. For Bricks users, JetEngine support has improved significantly in recent versions.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.