-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search in the UV not working #175
Comments
This wasn't working due to mixed content error seen in the console. Once I marked the tenant as ssl_configured: true, the search works again - No code changes were needed. @KatharineV ref: |
I tested on ADL prod, and the UV search worked. Yay! But the UV search is still not working in staging. |
@KatharineV This is resolved by setting the ssl_configured to true for the tenant ref: |
Thanks, @ShanaLMoore . Is the Ssl feature one that I need to flip on for all our tenants? If so, can you tell me which part of the dashboard is showing in that screenshot above? I can go through all the tenants and make sure it's on. |
We were just talking about if we should consider creating a ticket to turn ssl_configured on by default for everyone since it definitely seems to be the way you'd need it. You go to admin dashboard. In the left column click Settings > Account. Scroll all the way down and check the checkbox for ssl_configured. Click Save Changes. |
Thanks! I've set Ssl configured to True for all the (in-use) tenants in B2 and S2. |
After Knapsack, the search box in the UV is not working. The example document below contains the word "work" multiple times, so I assume that Tesseract caught at least one of those instances. The word "work" should be searchable. When I enter the word in the search box and hit enter, I get a spinning circle that never resolves. The word never highlights and I don't get an error message or anything.
https://adl.b2.adventistdigitallibrary.org/concern/generic_works/wdf_0010_005_the_nashville_sanitarium_ellen_g_white_extracts_from_lette?locale=en
The text was updated successfully, but these errors were encountered: