webgobe

Got that, thank you. I did my experiences too, to see how the link is actually generated for these cases. Seemingly until you have an accented first letter in the list, that will be picked up for the Alphabar, the unaccented character is used only when you don’t have any accented character in the definition list.

So take this as a feature request, for some future version of the plugin you might consider to slightly tweak the SQL request to produce the list to have the unaccented first characters on top – this might solve the issue without too much effort. Anyway, I love the plugin, I am using it on ~10 sites, and this annoyance will not stop me from that ;).

Thank you for your great work so far! As an Open Source plugin developer I know how much work is invested in building and supporting such a plugin, and I am truly appreciating your efforts.

I got that, I am building multilingual sites for 25+ years ?? I understand all the problems handling international characters can create!

So, to be clear, I want a SIMPLE thing: if I have glossary terms with u, ü, ú etc in the alpha bar and in the URL for that page to have the letter U.

Seemingly in the above page the last glossary term’s first letter is picked up for the Alpha bar AND for URL.

I would be happy with a working dirty trick which does the same like: IF I am taking care to have the LAST glossary term in the list beginning with unaccented character to have the desired result – I can live with this – just need to know in what order Glossary picks up the terms to build the list to be able to trick it ??

Upgrading to 2.0.3 fixed the issue, THANK YOU!

I also had a fatal error, but I have no Woocommerce or addons for it. Needed to restore the site from backup, since nothing worked.

I tried those steps already. (I am a professional web developer). That’s why I asked for help, because nothing worked. Things are looking ok, and from top bar I can launch the popup, nothing unexpected in debug. Just simply isn’t starting, none of triggers are working.

I exported them from the translation interface you pointed me to…
https://translate.www.ads-software.com/projects/wp-plugins/glossary-by-codeat/

Added both updated files, BTW, you can check in your end too!

Aha, ok, lets do that too then. ‘Will get back to you if that does not fix my problem.

Done, you should get the mail already.

Also, I accessed the translation as you suggested and added some 5?+ string translations:
https://translate.www.ads-software.com/projects/wp-plugins/glossary-by-codeat/stable/hu/default/

glossary-by-codeat-hu_HU.po is the name of the .PO file in the -wp-content/languages/plugins directory.

Daniele, I tried that already, I translated the .po file. The string isn’t there – seems to be a Taxonomy related thing.

Thank you! This fixed it. somehow overlooked this setting ??
Denes

Mistery solved!!
So it is a feature, not a bug ??
Yes, I can confirm, that this fixes the behavior (or, more precisely, exhibits the default behavior).
Thanks, Merv, you’re the best!

Do we have a fix available somewhere? I also would need it…