This continues to be a VERY BIG issue when using the PRO version of the plugin together, does anyone care? Is anyone supporting this “premium” plugin anymore? I have lodged support tickets directly in the website portal as well and I’m being ignored??
Hello? Is the pro version of the plugin no longer being supported or updates released to be compatible with the base version???? Can someone please respond?
Hi, Please update latest version 3.3.22 we have checked the compatibility issue, Please let us know if you have any issues?
Regards
Thank you for the reply. Currently now running Post Grid 2.3.23 and Pro 3.3.22, still returning “no posts found” error.
Reverting back to Post Grid 2.3.19 and Pro 3.3.21 and the issue is fixed again. I posted an AI code review of what the issues might be in my pro account support ticket, but have had no response there either.
AI debug tools have reported the following, if it helps…
Main issue: the newer free ZIP is 2.3.23 (not 2.3.21) and it removed the free plugin’s filterable query-loop implementation.
In 2.3.19, free plugin loads:
templates/view-filterable/index.php
and that file registers:
add_action('post_grid_builder_viewFilterable', ...)
It also registers/enqueues MixItUp scripts needed for filterable results.
In 2.3.23, that include is gone. So when shortcode rendering calls:
do_action("post_grid_builder_" . $viewType, ...)
a saved grid with viewType = viewFilterable has no callback, producing empty/0 output.
The Pro plugin still assumes filterable support exists. It adds query/filterable behavior, e.g. sets filterable queries to posts_per_page = -1 and adds filterable classes, but it does not replace the missing free viewFilterable renderer.
Secondary issue: 2.3.23 added aggressive wp_kses_post() wrapping around recursive builder HTML. That can strip Pro-generated attributes/markup and cause additional front-end/editor errors.
Fix direction: restore the removed templates/view-filterable include and script registrations from 2.3.19 into the newer free plugin, or move that renderer into Pro. Also review the new wp_kses_post() wrapping in includes/functions-builder.php; it is likely too destructive for Pro output.