Forum Discussion

Claudius's avatar
Claudius
Boss
2 months ago
Solved

24.10 API change breaks navigation

Staging instances of two three communities I work with got upgraded to 24.10 and for both all the Khoros supplied theme-lib.community-header-navigation broke as a result with the error:

Freemarker template 'theme-lib.community-header-navigation' processing failed:
InvalidReferenceException:The following has evaluated to null or missing:
==> restBuilder().method("POST").path("/search").body(liql_query).call().data.items  [in template "theme-lib.community-header-navigation" at line 188, column 62]

I haven't done any in-depth investigation or how to come up with a fix. On quick glance neither the  Communities Classic v24.09 Release Notes nor Classic Communities: 24.10 Release Notes do contain any suspicious change.

Just wanted to share so you folks got a starting point.

  • Claudius's avatar
    Claudius
    2 months ago

    And to wrap things up: Khoros Engineering meanwhile fixed this issue. Should you still see this on your (stage) community in December 2024 make sure to ask Khoros support to get that fix deployed on your community, too.

    If you run into this issue at a later stage... you probalby should open a new topic :)

5 Replies

Sort By
  • Claudius's avatar
    Claudius
    Boss
    2 months ago

    The weird thing is that where this component breaks keeps changing (And debugging it is made trickier because the component usually gets cached), e.g. sometimes the exception thrown is something like:

    InvalidReferenceException:The following has evaluated to null or missing:
==> nav.view_href  [in template "theme-lib.community-header-navigation" at line 82, column 44]

    ...or

    So I'm wondering if this is search re-indexing not having caught up after the 24.10 upgrade and / or caching of an invalid state?

  • Akenefick's avatar
    Akenefick
    Genius
    2 months ago

    I am seeing something similar in our stage. I have narrowed it down to customizations using restBuilder I think. I opened a support case. Our stage was also just upgraded to 24.10

  • Claudius's avatar
    Claudius
    Boss
    2 months ago

    You know I love hats 🤠 So I'm now switching to my Khoros Support hat by sharing the reply I got from my ticket:

    The navigation component issue has been identified as a bug and the ticket has already been filed with our Engineering to fix it. We have seen that most customers have reported the same, so we have raised the priority of the ticket, and our engineering team is actively working on this to get a quick fix.

  • keithkelly's avatar
    keithkelly
    Leader
    2 months ago

    I've been experiencing the same and have received similar responses from support.

  • Claudius's avatar
    Claudius
    Boss
    2 months ago

    And to wrap things up: Khoros Engineering meanwhile fixed this issue. Should you still see this on your (stage) community in December 2024 make sure to ask Khoros support to get that fix deployed on your community, too.

    If you run into this issue at a later stage... you probalby should open a new topic :)