Terms not appearing in glossary, macros throw error rendering viewing term page

[Mark Montminy]

I’ve just installed Glossary version 4.4.2 in our production instance. We’d previously been evaluating in a test environment.

After creating the first terms the pages are created, the Terms shortcuts are created, but viewing the Glossary from the nav bar shows no terms. If I view the page created the Translations macro renders, but the Term Info macro shows Error rendering macro 'glossary-term-info' null

The tip of the stack shows:

java.lang.NullPointerException
        at com.wknowledge.atlassian.confluence.glossary.macros.TermInfoMacro.execute(TermInfoMacro.java:72)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at com.atlassian.confluence.macro.xhtml.XhtmlMacroManager$ResourceAwareMacroInvocationHandler.invoke(XhtmlMacroManager.java:208)
        at com.sun.proxy.$Proxy3711.execute(Unknown Source)
        at com.atlassian.confluence.content.render.xhtml.view.macro.ViewMacroMarshaller.executeMacro(ViewMacroMarshaller.java:226)
        at com.atlassian.confluence.content.render.xhtml.view.macro.ViewMacroMarshaller.marshalInternal(ViewMacroMarshaller.java:147)
        at com.atlassian.confluence.content.render.xhtml.view.macro.ViewMacroMarshaller.lambda$marshal$0(ViewMacroMarshaller.java:104)
        at com.atlassian.confluence.impl.content.render.xhtml.analytics.MetricsCollectingMarshaller.marshal(MetricsCollectingMarshaller.java:49)

This is blocking our deployment.

I’ve checked content indexing, no issues shown. I’ve tried disabling/re-enabling the addon. I’ve tried re-indexing the glossary itself.

All of the addon modules are enabled.

[Support wKnowledge]

Hi Mark,

many thanks for reaching out.

May I know please your Confluence version?

Could you please check if Glossary status are properly displayed?

For that you need to go to Glossary management then Workflow.

If no issue is encountered could you please recreate another term.

The team is awaiting your feedback.

Many thanks for your collaboration.

Best regards,

Jennifer

[Mark Montminy]

Confluence Server version 7.13.7, same as our test instance.

Workflow and statuses are properly displayed.

Adding a second term to the global space did seem to work, it is now recognized as a term, but the original is still throwing an error.

I then tried to do a bulk import of pages with the glossary-term label to pick up the pages that aren’t being treated as a glossary page, and it throws a nullpointerexception error as well in the logs and does nothing.

[Mark Montminy]

Are there any updates to this? While it mostly appears to be working, I believe we still have a problem with the 1st term being created in spaces not getting recognized as a term.

My main concern is that whatever is causing these errors creates a bigger problem later on as we expand our glossaries.

[Support wKnowledge]

Hi Mark,

Could you please send us the Confluence log file to [e-mail]?

When you created the first term the Glossary app is not yet configured. For that you need to delete it.

Many thanks,

Best regards,

Jennifer

‌

[Support wKnowledge]

Hi Mark, A new version has been released 4.5.0 which resolves the issue.

Many thanks, Best regards, Jennifer