[SOLVED] Message at bottom of builder screen: "No results found"

Bricks Version: 1.5
Browser: Chrome Version 104.0.5112.101
OS: Windows 11
URL: N/A

I am seeing a white space in editor when I scroll all the way down and it shows several “No results found” messages in it. I am not sure what I am doing when it happens. I will try to figure out what exactly is triggering it.

You might look at this post. Seems to be a new random problem. Bricks 1.5 interface problem - #2 by omega

1 Like

Hi macksix,
Thank you very much for your report.

I need some more information as I have never encountered this issue before.

  1. Have you disabled all plugins?
  2. “No results found” is the classic query loop message when there are no posts - do you have one or more query loops + infinite scroll enabled somewhere on your page?

It would be best if you send us the access data to the site and a link to this thread by mail to help@bricksbuilder.io so we can have a look.

Best regards,
timmse

  1. All plugins are disabled.
  2. I have no query loops or infinite scroll.

Sending email.

I found how to trigger it.

  1. Add a container with an image and a rich text editor.
  2. Highlight the text and click the Edit/Insert link button on the rich text editor toolbar.
  3. Type in any URL in the field that pops up and click the blue enter button.
  4. Click on the Image in the builder page view.
  5. Click the rich text editor.
  6. Repeat steps 2 & 3.
  7. Scroll the edit panel down and notice a white strip and see “No results found.” text showing.
  8. Repeat steps 5 through 7.

Each time a new line “No results found.” is added.

See screencast: Recording #25

1 Like

I believe it’s coming from the autocomplete script. It’s looking for the pages when the user starts typing in the link search field. The ‘no results found’ should be hidden as it’s supposed to be there for accessibility only, but not visible (as far as I can tell).

1 Like

Thank you so much for the video & step-by-step instructions. I was able to replicate the issue.

It’s like @wplit said, and caused by the result of the autocomplete script. Which generates those messages and adds the HTML to the .ui-helper-hidden-accessible div on the page (for accessibility). Like the WordPress .screen-reader-text it should be available in the source code, but not displayed. We’ll provide a fix in the next update :call_me_hand:

1 Like