Developer Forum »
Error when clicking "Add existing"
Reply to thread
47 posts
Reply Quote
Anna Madsen
25.02.2021  10.33

Hi, we're getting an error for Relatude version 5.0.2109.

When clicking "Add existing" for a relation field, no objects are displayed. Instead, an error message is shown saying either "Cannot read property 'LCID' of null" (test environment) or "s is null" (locally). This is not an issue in the production environment which has relatude version 5.0.2100.

I've ran all "Ensure..." jobs in /waf/setup in addition to "Update database and start website" without this fixing anything.

This is a bit urgent as we plan to have a deployment next week, and we don't want to deploy anything which is not functioning.

Attachments
181 posts
Reply Quote
Vidar Langberget
25.02.2021  10.45

Hi!

There has been a several fixes regarding languages in the last few releases. Could you try to upgrade to the latest version?

 

Vidar

 

47 posts
Reply Quote
Anna Madsen
25.02.2021  11.31

Hmm, I tried updating to 5.0.2113 locally
The issue seems to still be present

181 posts
Reply Quote
Vidar Langberget
25.02.2021  11.39

Does it happen on all relation properties or only some of them?

47 posts
Reply Quote
Anna Madsen
25.02.2021  11.57

The same error is there for the following relation classes:

  • ContentParentPropertyClass
  • ContentChildrenPropertyClass
  • NodeParentPropertyClass

As for ContentParentsPropertyClass, I was not able to test it properly.

181 posts
Reply Quote
Vidar Langberget
25.02.2021  12.23

Hi!

The issue should be fixed now. Could you reload the admin UI and login again? 

 

47 posts
Reply Quote
Anna Madsen
25.02.2021  12.28

Hi, and thank you for the help.

Now it seems to work both locally and in test :)

Can I ask what the issue was?

181 posts
Reply Quote
Vidar Langberget
25.02.2021  12.30

We've been improving the language handling in the admin UI lately. The problem here was that the "Add exisisting" dialogue reuses a common component used in other parts of the UI. The dialogue in question is a special case, and it needed to be initialized differently in the context it was used. We knew we had tested the component thoroughly after the change, but we didn't catch the special use-case.

1