Crocoblock plugin review and common issues

JetSmartFilters must be connected to a specific JetEngine Listing or a JetEngine Query. In the JetSmartFilters widget settings, set the “Filter ID” to match the Query ID configured in your JetEngine Listing Grid widget. Both widgets must reference the same query. Also verify: (1) the filter type matches the data being filtered — a taxonomy filter requires the post type to use that taxonomy; (2) the filter’s data source (meta key name or taxonomy slug) exactly matches the field registered in JetEngine; (3) published posts with the filtered values exist — if no posts have the selected value, zero results correctly return.

Verify JetBooking’s date conflict checking is enabled in JetBooking → Settings → Advanced. The conflict check prevents overlapping bookings for the same “apartment” (bookable item). Ensure: (1) each bookable item is registered as a separate JetBooking “Apartment” — conflict checking is per-item, not site-wide; (2) the booking form uses JetBooking’s native date picker (not a custom date field) — custom fields bypass the built-in conflict logic; (3) if using WooCommerce for payment, the order completion webhook must mark the booking as confirmed to block those dates from future availability.

In the JetEngine Query Builder (JetEngine → Query Builder → [query name]), click Preview to test if the query returns results. If Preview shows results but the Listing Grid does not display: (1) verify the Listing Grid widget has the correct Query ID selected; (2) clear Elementor editor and page caches; (3) check browser DevTools Network tab for failed AJAX requests when the grid loads. If Preview shows no results: review the query filters — check meta query conditions for correct meta key names (case-sensitive) and comparison operators. An incorrectly configured meta filter returns zero results even when posts exist.

The standard Crocoblock directory stack: (1) JetEngine to create the custom post type (Listings), register meta fields (location, category, price), and create a Query Builder query for listing display; (2) JetEngine Listing Builder to design the listing card template (thumbnail, title, category, key attributes); (3) JetSmartFilters to create filter widgets (search by keyword, filter by category, price range, location); (4) JetEngine Listing Grid on the directory page, connected to the Query Builder query, with JetSmartFilters widgets positioned above or beside it. The filters connect to the grid via a shared Filter ID.

JetWooBuilder creates custom Elementor templates for WooCommerce pages (single product, shop archive, cart, checkout, account). Go to Crocoblock → Theme Builder → Add New Template → Single Product. Design the single product layout using JetWooBuilder’s WooCommerce-specific dynamic widgets: Product Images, Product Title, Product Price, Add to Cart, Product Description, Product Tabs, Related Products. Assign the template to all products or specific product categories. This replaces the default WooCommerce single product template with your fully custom Elementor-designed layout.

For a freelancer building 3+ data-driven sites per year (directories, booking platforms, job boards, marketplaces), Crocoblock’s All-Inclusive Personal subscription ($384/year) pays for itself through reduced custom development time. For freelancers building standard business sites with Elementor, Essential Addons or ElementsKit at $39/year provide adequate capability at a fraction of the cost. Crocoblock’s value scales with site complexity — the more sophisticated the data architecture requirements, the more the JetPlugins suite justifies its cost.

Increasingly yes. JetEngine, JetSmartFilters, JetFormBuilder, JetStyleManager, and other JetPlugins have native Gutenberg (Block Editor) support. JetWooBuilder remains Elementor-only. For new projects where Bricks Builder or Gutenberg is preferred over Elementor, many of Crocoblock’s core dynamic content capabilities (custom post types, filtering, forms) are available without Elementor. Full feature parity with the Elementor versions has not been reached for all plugins, but the Gutenberg expansion is actively developed.

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.