[vincentb]

You cannot access this content.

[vincentb]

You cannot access this content.

[vincentb]

You cannot access this content.

[vincentb]

You cannot access this content.

[vincentb]

Thank you Ernest for troubleshooting this!! Definitely an improvement: browsing to the search page gives the right results (including paging) when initially rendered! However after a quick test I found some variations that are still showing bugs:

1- Only the first page of results is matching the expected results when refreshing the page or navigating directly to the URL from the previous search (e.g., navigate to /search5, refresh — or copy URL, open new tab, paste URL).
2- Toggling options between all / appreciation=2 / appreciation=3 (special test value), produces inconsistent results (sometimes the wrong results are shown after the first page of results, sometimes the number of results is incorrect).

I have modified slightly the same test case to use again Infinite Scrolling, to ease testing.

I think we are on the right track. Would you please investigate the other 2 potential bugs and let me know?

• This reply was modified 3 years, 9 months ago by . Reason: added more precise description of the bugs

[vincentb]

You cannot access this content.

[vincentb]

You cannot access this content.

[vincentb]

You cannot access this content.

[vincentb]

You cannot access this content.

[vincentb]

You cannot access this content.

[vincentb]

You cannot access this content.

[vincentb]

You cannot access this content.

[vincentb]

Thanks Ernest for your reply.

I am using very few plugins, and no other Elementor plusins (just Elementor/Elementor Pro). I tested by deactivating all plugins except Elementor/ACF/CPT UI/Ajax Search Pro, and the results are the same: both problems still happen.

Here is some additional info on this specific test case which allows me to reproduce the problem consistently (although there are multiple other situations happening):
– ~1200 posts, all using one custom post type which is leveraging ACF custom fields
– the “appreciation” field was created using ACF, of type numeric, optional
– many posts have the appreciation field not filled
– 33 posts have the appreciation field set to numeric value 2
– a search page is set up to have only the 2 elements described in my original post, so all posts matching appreciation==2 can be displayed in-place in this page
– the “Posts” block (element E2 described in my original post) is set this way in Elementor Pro:
– Layout options: Skin=Cards, Columns=6, Posts per page=24, everything else turned off (so only showing a 300×300 image for each result)
– Query options: Source=book (my custom post type), everything else left as defaults
– Pagination options: Pagination=Infinite Scroll
– Ajax Search Pro instance’s settings:
– not showing search bar, just the appreciation custom field
– Frontend Search Settings are configured only for Custom Fields, and just the “appreciation” custom field: “appreciation” post meta, Type=radio, Radio values=
||All
2||Preferred**

More info of the behavior observed:
– Navigating to the search page shows the 2 radio buttons, with the second selected by default as expected
– Search results are shown but have nothing to do with the selection made (not matching with appreciation=2)
– Scrolling below the first page of 24 results shows up to hundred posts, all unrelated with the search
– Switching from “Preferred” to “All” refreshes the search
– Switching from “All” to “Preferred” refreshes the search but does not filter properly
– Refreshing the page (F5 in Edge) reloads the page with a first page of results showing as expected (all appreciation=2)
– Scrolling below starts showing results unrelated with the criteria

If I set Posts Per Page=50 (more than the expected number of matching posts), refreshing the page displays the expected results and scrolling doesn’t show unrelated results.
If I set Posts Per Page=4 (less than the page can display), refreshing the page displays 4 expected posts, and stars loading unrelated posted right after them.

• This reply was modified 3 years, 9 months ago by . Reason: added interesting test case with only Posts Per Page=4, showing that only the 1st page is relevant when refreshing

[Author]

Posts