vcb

@ewolfram you could try to limit the function to be “active” only on the post type(s) or pages you need with a simple if/else.
A newer WP update might have changed some internals which could break things any time.

The above code is highly customized and does work just as a snippet, no updates guaranteed nor promised ??

sry, messed up – wrong plugin/thread. ty

@awelzel : thank you so much. Your input helped me to see it from a different perspective… Error was related to some custom code within functions.php.

@bmartinent : I’ve been able to solve the issue. It’s been weird, but it had nothing todo with glossary plugin itself. Solved it by fixing my custom functions.php code. Ty for trying to help.

Also I don’t really understand why the PHP causes JS troubles.
Do you suspect any code-part?

SOLVED: Unlimited Version was not up to date. Thanks @eddie

I ran into the same error, but don’t use “all-in-one-wp-migration-file-extension” at all.
Further I do own the unlimited / pro version. Is this still due to wrong server config? Ty

@yas-se I’ve used the following to force “open” each glossary entry within the glossary page; put it into your style.css

.mywpglossary-list-entry-description {display:block!important}

Update: When I use php 7.4 the html glossar term uses/generates the following html link:
I guess you kinda suspect where this error resides? Would you mind sharing it, this way I could have a look without spending too much time searching for the exact code-snippet within your source

<a class="mywpglossary-definition" href="https://localhost/testpage/glossar/#testglossar">Testglossar</a>

Thanks Bastien, looking forward to it.
Great Plugin, I do really like it.

@yas-se
I had the same issue and worked around it by using another search input. This way a user can search within the glossary page the same way you’d be using CTRL+F; but within the html instead of a pop-up.

@bmartinent : feel free to include it in your next update…

<div class="searchterm">
	<p>SEARCH:</p>
	<input placeholder="..." type="text" id="searchterm">
	<input id="myBtn" type="button" value="SUCHEN" onclick="search(document.getElementById('searchterm').value)">
</div>

<script>
function search(string){
	window.find(string);
}

// Get the input field
var input = document.getElementById("searchterm");

// Execute a function when the user presses a key on the keyboard
input.addEventListener("keypress", function(event) {
  // If the user presses the "Enter" key on the keyboard
  if (event.key === "Enter") {
    // Cancel the default action, if needed
    event.preventDefault();
    // Trigger the button element with a click
    document.getElementById("myBtn").click();
	//alert(document.getElementById('searchterm').value);
	//document("\"mywpglossary-term-"+document.getElementById('searchterm'\").value).click();
  }
});
</script>

Thanks for the note Bastien. I’ve been digging a bit deeper; please see the following details:

It looks like the data-url is set correct:
class=”mywpglossary-term-def” data-title=”testglossar” data-url=”https://localhost/testpage/glossar/#testglossar

Is there some js-script which forwards to the glossary term in case a user clicks on it?

Another weird thing I don’t know what/why this happens. I’m getting the following console.log warnings, regardless the php version (7.4/8.x), Brave Browser:

DevTools failed to load source map: Could not load content for https://unpkg.com/@popperjs/popper.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for https://unpkg.com/tippy-bundle.umd.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

When I try to download the scripts manually it results in an error:
Cannot find package @popperjs/popper.min.js.map@latest

Can you tell what’s happening here?

Thanks for pointing this out Kathryn. “Order” attribute is exactly what I’m looking for to be the orderby value. Do you see a way to include it in @thelmachido function?

The function also works on pages. “Order” field is part of a fresh WordPress installation; please see the attached screenshot.

• This reply was modified 1 year, 6 months ago by vcb.

sure; please see attached image, at the bottom you can see the page attribute – sort order:
Reihenfolge = Sort order
https://ibb.co/z4y8ZGz

*typo* order.ty = orderby