7.6.3 - Search facet filters reload or cache problem after changing search term on results page

[ovali]

Describe the bug

On the search results page the search filters will fail to load when changing the search term again and redo the search.
Only the placeholders will be visible and the amount is equal to the ui DefaultAppConfig value for filterPlaceholdersCount

To Reproduce

Backend and Frontend is 7.6.3.
The testsystem is Ubuntu 22.04.5 LTS / OpenJDK 11.0.26 / Node 18.18.0 / PG 14 / Solr 8.11.4 and 9.7.
In my case the bug appears with and without apache as proxy.

Steps to reproduce the behavior:

1. Perform a search with entering a term into the header-search-box.

2. The results page show up with results and the search filters

3. Change the search term in the search box and press the search button

4. The search results will be reloaded but the search filters are not visible anymore.

5. Do SHIFT-reloading the browser and the filters appear again.

There are no errors in console or log files.

Additional information

Related to Tim's advice the ui-universal settings enableSearchComponent and enableBrowseComponent will not make any difference in behaviour.

Also backporting #3888 does not change the behaviour in my case.

Expected behavior

The search filters should always be visible.

[ovali]

#3907

Alan describes the same bug

[pnbecker]

This cannot be reproduced on demo.dspace.org which currently runs on DSpace 8.1. We also cannot reproduce it on our custom DSpace 8.1 instance. I have not tested it on DSpace 7.6.3, but as @alanorth discoverd this issue and as I know @ovali personally, I would see this as a confirmed bug in DSpace 7.6.3. It's very helpful to have a way to reproduce it on vanilla DSpace 7.6.3.

Thanks @ovali to describe a way to reproduce this issue.

[tdonohue]

For the time being, I've pulled this over to our 8.x & 7.6.x maintenance board. But, I agree that this needs to be reproduced on a vanilla DSpace 7.6.3 installation. Nonetheless, since at least two sites are encountering this, I'm going to assume there may be a bug here. My mistake, I see this was reproduced in a vanilla DSpace 7.6.3 based on the discussion in Slack.

This needs a volunteer to verify on out-of-the-box 7.6.3. If verified, it needs to be fixed. As noted above, this is not reproducible in 8.1.

[tdonohue]

@FrancescoMolinaro and @atarix83 : I wanted to highlight this issue for you because this appears to be related to the backport of #3709 to dspace-7_x (in #3907). For some reason that backport may not be behaving the same as the fixes in 8.x.

If you (or someone on your team) are interested in claiming this bug ticket, please let me know.

[sergius02]

Hi!, in @arvoConsultores we have solved this. We can do a pull request with the fix.