We have several glossary terms added to a localized version of a couple smooshed together OpenStax books, but the definitions are not appearing in the web version of the book when you click on them. The glossary works, but the in-text terms do not display the definitions. I’ve followed all of the procedures listed in https://guide.pressbooks.com/chapter/glossaries/ and was wondering if there is something I am missing.
Jeremy,
I was able to get glossary terms to pop-up and display correctly, but only after expanding both of the collapsed sections (strange!). See screenshot below, I’m going to see if I can replicate on other networks/books that use collapsible sections. If I can, this looks like it should be filed as a bug – probably related to some kind of javascript conflict.
Tried to recreate it on one of our hosted networks and wasn’t able to reproduce the problem. See https://integrations.pressbooks.network/testclone/chapter/multi-section-chapter-with-glossary/. Would you be willing to post the contents of your Diagnostics page (available in the admin footer) to see if others might be able to identify anything that might be causing JS conflicts for you?
Platform: OS X
Browser Name: Chrome
Browser Version: 80.0.3987.100
User Agent String: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.100 Safari/537.36
WordPress Configuration
Network URL: http://openbooks.library.umass.edu/
Network Type: Subdirectory
Version: 5.3.2
Language: en_US
WP_ENV: Not set
WP_DEBUG: Disabled
Memory Limit: 64M
PHP Version: 7.2.24-0ubuntu0.18.04.2
MySQL Version: 5.7.29
Webserver Info: Apache/2.4.29 (Ubuntu)
PHP Configuration
Safe Mode: Disabled
Memory Limit: 256M
Upload Max Size: 8M
Post Max Size: 8M
Upload Max Filesize: 8M
Time Limit: 30
Max Input Vars: 1000
URL-aware fopen: On (1)
Display Errors: N/A
Thanks Jeremy. I cloned the book in question to a testing network we host and can’t replicate the issue there either (see https://integrations.pressbooks.network/physics132/chapter/chapter-1/). I combed through the <head> sections on both pages and really don’t see much difference.
Here’s what I am seeing on your book though – when I expand the first section (but not the second) and click on the first glossary term – here’s the resulting html for the tooltip element: <div class="glossary__tooltip glossary__tooltip--visible" id="5-92" x-placement="bottom" style="position: absolute; will-change: transform; top: 0px; left: 0px; transform: translate3d(569px, 286px, 0px);"
Once I expand the second section, the resulting html is: <div class="glossary__tooltip glossary__tooltip--visible" id="5-92" x-placement="bottom" style="position: absolute; will-change: transform; top: 0px; left: 0px; transform: translate3d(569px, 286px, 0px);"
The difference between the two is the translate3d value. The tooltip is being activated in the first case, as intended, it’s just not appearing in the visible area of the page because the translate3d value is being miscalculated. Still not sure why that would be the case, however.
In other words, I think that your book is calculating the wrong X (horizontal) position for the tooltips on glossary terms until the second collapsed section gets expanded. Don’t know why that is – my recommendation would be making sure you have latest versions of Pressbooks (5.14.0) McLuhan (Pressbooks Book 2.9.2), and Jacobs (1.2.1) and then reporting back if problem persists after updates.
I am usually prompted to update themes and the PB plugin on the Network admin screen. We are not on these latest versions and it doesn’t appear that we can update from there. Is this something that has to be done on the server side?
