SOLVED: Infinite Scroll + Condition

Bugs
1

Browser:Chrome Version 122.0.6261.129 (Official Build) (64-bit)
OS: Windows 11
URL: https://irgc.mybiz.cy/activity-status/reported-involvement/
Video: https://youtu.be/nMhacGp3G4g

  • Set element condition
  • Shows fine in initial query
  • When scrolling to load more, element with conditions will not display

image

2

Hi Cyrus,
Thanks so much for your report!

Unfortunately, I cannot reproduce the issue. Would you be so kind as to provide more details about the conditions, best in a screencast using https://jam.dev showing and explaining what the condition does?

Best regards,
timmse

3

thanks for a quick reply.

I hope this helps.

https://jam.dev/c/f3bd2689-97aa-492f-8310-afb7bfd7cd66

4

Perfect, Thanks so much for the video!
Now I’m able to replicate the issue. The archive title returns “Archives” as soon as the infinite scroll triggers.

1 Like
5

Any fix for this yet?

6

Unfortunately, not yet. It’s currently “in progress,” but I can’t tell you an ETA.

1 Like
7

Hi @CYrus ,

I just rewatched your recent video. (Jam)

Noticed 2 points here:

  1. Infinite scroll returning incorrect term posts.
  • Please set the query as “Is main query” and try again if any irrelevant post displayed in infinite scroll.
  1. {archive_title} not usable in infinite scroll:
  • Understand this is an issue, because Bricks is using get_the_archive_title function to retrieve the current archive page title. However, get_the_archive_title is not working inside the REST API call (Infinite scroll, AJAX popup, or Query Filter AJAX) because no main query in REST API.
  • Any specific reason must use {archive_title} as condition for the looping posts?
  • Instead of using {archive_title} as the condition, if your main purpose is only to display the button for any post’s activity-status taxonomy is “Reported Involvement”, you can use {post_terms_activity-status:plain} contains Reported Involvement in the condition area. Can you try this approach?
    image

Regards,
Jenn

1 Like