Updated to BioKIC and now missing nav menus

[foozleface]

In the occurrencetabledisplay (accessible via "Edit existing occurrence records" from collections) we noticed that the nav menus vanished. Sad!

Turns out that the css tag "navpath" is being hidden (display:none, or .hide() ) somewhere. Changing this css tag makes the menu show up, but I'd like to know the underlying intent here; I'm guessing this is configurable someplace.

Screen shots show the difference. Note the "1-1000 of 304760 records" which is missing by default in BioKIC.

Any guidance welcome.

[themerekat]

Thanks for alerting us to this @foozleface ! Which portal are you using in this instance?

[foozleface]

CAS hosts our own, until recently based on the 2015 EOLed codebase. We're upgrading to BioKIC now and doing QA on it, and this popped out. Portal is closed at the moment; Log4J wasn't worth patching in solr and it's a good excuse to do the rollout.

[themerekat]

Thanks for the clarification. I don't think this has shown up on any of our portals.
@egbot , any advice?

[egbot]

I can't find anything in the code that is hiding the navpath div, or any other related elements. I just did a new install to verify this. Are you sure it's not being done within an old css file that you brought in via the /includes/head.php file?

Note that we have remove SOLR indexing for the BioKIC version of the code. Only a couple portals really need it, and it was causing more issues and security vulnerabilities than value added. Instead, we have working on improving native index via more efficient code and db schema modifications. However, there are a couple portals that still need enhanced indexing, and thus we plan on bring that functionality back in the near future.

[foozleface]

Thanks for checking - tracing back through head.php was a great tip.

`#innertext a {} #innertext a:hover {} div.navpath {

padding-top: 8px;

padding-bottom: 0px;

padding-left: 10px;

margin-bottom: 0px;

text-align: center;

color: #679146;

display: none;

}`

That would certainly do it.

We are delighted to see the end of solr. Good database design is the way to go!