I just saw, in the frontend I get more information:
Warning: usort() expects parameter 1 to be array, null given in /www/htdocs/w01b656e/wp-content/plugins/glossary-by-codeat/frontend/Core/Terms_List.php on line 139
Thanks a lot
I am releasing a new version with the fix but do you have any glossary terms?
Hi Daniele
Thanks in advance for the bugfix. And yes, I had one glossary term. In the meantime we played around a little more, added two more glossary terms and the error message went away.
While we‘re at it. I‘m using the theme Divi. When I enable the divi builder for a glossary term everything is fine on the glossary term page. But the tooltip is empty. Is it possible to have an additional content field – like the excerpt field for pages and articles – that holds the text of the tooltip?
Thanks a lot
Uwe
I am receiving the same error message. I had to rollback the plugin to version 1.8.18 to get a functional version of “Glossary”. What is going on?
Good thing the error on my site only occurred when I attempted to edit or create a new post. Otherwise the site was functioning fine.
Hi @kemmettchris,
do you have the same error with glossary 2.0.10 that I released yesterday?
That version should have the fix.
If I can get more info I can fix the issue ASAP.
We released the new major after 6 months of works and did a lot of tests, but they weren’t enough for all the users cases.
For @macangelo, we have various Divi customers where the plugin is working. I need a web page with the issue as I can investigate better.
The tooltip content get from the post content or the excerpt so if they were empty that is empty, instead if you want to put a different text from a different field this is not possible yet.
Hi Danielle
I just updated to Glossary 2.0.10.
On the webpage https://eyelikeit.com/seo-duesseldorf/ you should see 3 tooltips. For:
SERP (Divi) (–> https://eyelikeit.com/fachbegriffe/serp/)
Page Speed (no Divi)
Mobile Friendly (Divi)
Strange is also now that in the backend of “Edit Glossary Term” I don’t see the buttons to switch between Divi Builder and Standard Editor. But when I click in the space where the Divi Builder Button is supposed to be, the Divi Builder opens.
… strange
Thank you for your help!
I don’t see any tooltip.
Probably there are various issues in this page.
First one the HTML is too much nested because of a page builder, usually this is an issue with page builder and our system avoid parsing those cases to avoid HTML broken.
Second those terms I see they are already a link so our plugin ignored that, you should have those terms without links if you want that our plugin inject the links itself.
Also our plugin is confirmed that works with Elementor as page builder that is the most standard around and every page builder with the various version and non-standard behavior is difficult to do more analysis of the issue.
For premium users in those cases we have the refund in 30 days and a better support that let us to get access to the website so we can investigate with the code as we cannot replicate in our systems.
The error message seemed to be the same.
“usort() expects parameter 1 to be array, null given” ….
The cause of the error is different.
My error occurs only when I attempt to edit a post or draft a new post. So this is a big problem.
I have messaged you on facebook, so I can create a temporary login for you to look at the error. When you are ready just message me back.
I am trying to understand the issue, as 2.0.10 we have a check but I need to know the complete error so I can see if the last changes works.
In our local test system the error is not happening and that code is running only on frontend, so maybe you are using a page builder?
I released another bugfix for this few days ago.
If you see this issue again starts a new thread
