Site logo

Archived topic

Navigation Search CSS Wrong Only on Search Results Page

5 replies · Started by Weatherly on December 19, 2018

Viewing posts 1–6 of 6

On all the other pages its lined up properly. But we were getting terrible search results (as is usual for Wordpress) and so installed Relevanssi. As far as I know this shouldn't effect the css but something is wrong. It seems to break the nav bars somehow. If the Search button lines up on all the other pages it doesn't line up on the Search Results page. But if I try and fix it there it breaks elsewhere. Any ideas how I can fix this so we can have a decent working search?

No. It's the button itself not the bar: the little hour glass thing. If you type in a name that is on the site (Davis for instance) the page reloads to get to the search results with the little hour glass suddenly bumping the top of the nav bar instead of centered top to bottom.

I tried to fix but then the hour glass lined up on the search page but was no longer properly placed on the other pages.

Hi there,

i notice that when you go to the search page, all of your links/meta/scripts that should be located in the <head> are forced into the <body>

Can you try disabling any plugins you have and see if one of them is causing the issue?

It didn't start til I activated Relevannsi as far as I can tell. The trouble is we need the plugin or we get no search results. We are also using Staff List Pro, and without Relevannsi all the content from that is ignored in search results.

The odd thing though is I have used Relevannsi with GeneratePress several times before and it never caused this. (I've contacted them too just in case).

But it seems to be something about Relevannsi, Generatepress and the Staff List Pro that is clashing. :( And the if Staff List is the root they are the least responsive in support and very critical part of site!

Try this CSS as a temporary fix for the nav icon, whilst you wait for feedback from the plugin autors:

.search-item a:before {
    line-height: 49px !important;
}
This archived topic is closed to new replies.