WPIntell

Source evidence

No Posts Found

Post Grid · support · 2026-01-16T02:09:00+00:00

complaintsentiment
highseverity
0.92relevance
5replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 18 rows with source links

27.8% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

13 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
sarahsas resolved
Reporting an issue with the latest few updates of this plugin, possibly when working in conjunction with the PRO plugin, which I also use. When I upgrade to anything above Version 2.3.19, if I try to create a NEW post grid, no matter what query settings I use, it is consistently returning NO POSTS FOUND. I’ve tested this on two sites, one is using DIVI the other is using NEVE themes. I am using Post Grid Pro Version 3.3.21 on both sites. Old grids retain their queries fine, but I cannot build any NEW grids, it’s always NO POSTS FOUND. If I roll back the core plugin to 2.3.19, then I can create new grids again. Help? 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. Hello? anyone care? There are a multitude of compatibility issues popping up with the PRO version of the plugin now, can someone investigate and make sure they still work properly together please?

Comments

5 shown
sarahsas 2026-03-05T19:18:00+00:00

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??

sarahsas 2026-05-07T16:04:00+00:00

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?

hasanrang05 2026-05-08T12:05:00+00:00

Hi, Please update latest version 3.3.22 we have checked the compatibility issue, Please let us know if you have any issues? Regards

sarahsas 2026-05-08T19:12:00+00:00

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.

sarahsas 2026-05-27T15:36:00+00:00

Hello? anyone care? There are a multitude of compatibility issues popping up with the PRO version of the plugin now, can someone investigate and make sure they still work properly together please?