- This topic has 7 replies, 2 voices, and was last updated 3 years, 1 month ago by
.
-
Posts
-
Hi – I have a bizarre problem where we suddenly seemed to have lost a brand new search instance while in the middle of deploying. When i went back to my test page with the test instance, it also no longer shows results! The results box and all display results are just gone. All settings were unchanged and the preview works as expected, but nothing on the front-end works. At first I though maybe some home page elements were conflicting, but then we realized that the test search also failed.
Here is the test page:
https://www.spectrumsupplements.ca/a-test-search/
Let’s start by getting it working there again, please. Any ideas welcome!
I will buy 4 new licenses for clones of this site, once we have this figured out.
Bill
Hi Bill,
Don’t worry, we will figure it out in no time.
After a quick look on the front-end, I noticed, that there is a results shorcode placed into an invisible mobile menu container – which is present on the page, but not visible.
The results are basically propagated to that container, but because it’s invisible, it appears as if the search was not working.I can’t exactly pinpoint the of the shortcode, but it’s within a custom HTML block in a mobile only menu container in the header. If you remove that, then everything will work as normal again.
OK now I see – yes this was the HTML block where I attempted to place the search box. It works on the page now, but it will not work in the Flatsome menu structure…
Under Appearance > Customize you can access the layout options. Mouse over the header menu, for example and you should be able to select any of the elements to bring up the layout editor. In there I’ve tried Blocks and the HTML widget, both of which support short codes. Here is the shortcode I had in there:
[wd_asp elements='search,settings,results' ratio='30%,70%,100%' id=1]
This won’t work, despite working fine on the page itself.
Menus are generally very sensitive. The default menu structure is a “ul” unordered list with “li” list elements and also an “a” anchor tag for each menu item. These are inline elements and by HTML validity rules they can’t contain block type elements such as “div”. In modern browsers this is usually no issue, they render these incompatibilities just fine, but it is still problematic.
If you plan to place the search into the menu, I only recommend using the simple shortcode:
[wd_asp id=1]If it gets rendered it may work with the results hovering below it – or displayed within the page if the results shortcode is present.
OK so that does work in the menu area, however, is there anything to be done about the results box width? I’d like to have it wider than the current container of the search box.
Is that what the results short code is for?
- You must be logged in to reply to this topic.