Velo Glossary 1.11.0

Velo Glossary 1.11.0

• Terms that arrive after the page loads now get a hovercard. The script ran once and never looked again, so a term in a Q&A answer, a notification or anything else rendered by script was underlined with nothing behind it. Added nodes are watched, and window.veloGlossary.initHovercards( element ) wires a subtree on demand for scripts that would rather not wait.
• Only one definition shows at a time again, including cards opened in quick succession.
• Dropped the jQuery and hoverintent dependencies. Cards open on mouseenter with no delay, so hoverintent only ever reopened a card that was already up.

Velo Glossary 1.10.2

Velo Glossary 1.10.2

• Fixed terms being linked inside script, style and textarea. Since 1.10.0 the Bricks path scans a whole rendered element in one string, so inline scripts and styles inside it were scanned too. Linking a term in a JSON script breaks it for whatever reads it, and linking one inside a CSS rule breaks the declaration.
• Because a term is linked only once per page, terms spent inside that markup never reached the visible text. They do now.

Velo Glossary 1.10.1

Velo Glossary 1.10.1

• Fixed excluded class names having no effect in Bricks. A wrapper's class only excludes the text inside it when both are read together, and 1.10.0 read each text element on its own, so a class on a surrounding element never applied. Tab labels and before/after labels kept getting linked whatever was excluded.
• Glossary terms are now matched across a whole outermost Bricks element rather than element by element, which is how excluded tags and excluded class names already behaved in regular post content.
• Stopped linking terms in Bricks header and footer templates, so navigation and other per-page chrome is left alone.
• Replaced the velo_glossary_bricks_elements filter with velo_glossary_bricks_process_element, which decides per element rather than by element name.

Velo Glossary 1.10.0

Velo Glossary 1.10.0

• Added glossary term linking inside Bricks text elements. Bricks renders its own markup and only its Post Content element runs the_content, so terms written directly into a text element were never linked and no hovercard appeared. Scoped to the text and text-basic elements, filterable through velo_glossary_bricks_elements.
• Linked each term once per page rather than once per element, so a term repeated across several Bricks elements is only highlighted on its first occurrence.
• Skipped term linking inside the Bricks builder. The builder saves the markup it renders, and the frontend script removes the definition from the page on load, so a saved copy produced an empty hovercard.
• Moved the settings page from Settings > Velo Glossary to Glossary > Settings, alongside the glossary entries it configures. Saved settings are unchanged.

Velo Glossary 1.9.4

Velo Glossary 1.9.4

• Restored the classic editor for glossary entries so the Alternate Names, Associated Content, and Related Terms metaboxes render below the title as before 1.9.0, while keeping entries available through REST for builders.
• Excluded glossary entries from frontend search results when entry single pages are disabled, preventing search results that link to 404 pages.

Velo Glossary 1.9.3

Velo Glossary 1.9.3

• Re-enabled the block editor for glossary entries and marked the Alternate Names, Associated Content, and Related Terms metaboxes as block-editor compatible.

Velo Glossary 1.9.2

Velo Glossary 1.9.2

• Restored the classic glossary editor screen so Alternate Names, Associated Content, and Related Terms metaboxes remain visible while keeping glossary entries available through REST.

Velo Glossary 1.9.1

Velo Glossary 1.9.1

• Improved GitHub release notes so the WordPress plugin details modal has clean changelog formatting even when it falls back to release metadata.

Velo Glossary 1.9.0

Automated release for version 1.9.0. See readme.txt changelog for details.

Velo Glossary 1.8.0

Automated release for version 1.8.0. See readme.txt changelog for details.