You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discovered something like this independently. If you open the browser console, I expect you'll see an error saying such and such field can't be in filterableFields because it's not a vocab.
Such-and-such being one or all of cukSector, sicSection and locality.
Two solutions to this - well, four:
take out those fields from filtereableFields, have primaryActivity as the first and therefore the directory field.
revert the mykomap version to 3.0.4
alter mykomap to either implement the use of non-vocab (i.e. ad hoc) vocabs, or
alter it to silently drop them from the filters, as 3.0.4 does. This at least allows the directory to show adhoc vocabs. (Tantamount to option 2.)
I've gone for the first one for the moment, should now be redeployed. Which do you prefer?
take out those fields from filtereableFields, have primaryActivity as the first and therefore the directory field.
That is fine for now. We can schedule to do "alter mykomap to either implement the use of non-vocab (i.e. ad hoc) vocabs" later. DigitalCommons/mykomap#201
Describe the bug
The search panel is not opening properly
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The drop down filter options should appear below the search text box.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: