Missing Resource string after hot fix

Danny Winbourne asked on November 29, 2021 14:45

Might be related to https://devnet.kentico.com/questions/error-on-page-tab-after-upgrade

I have resolved an issue that stopped the page builder loading, which is great. However, I now appear to have a missing resource string when using either the page builder content or media picker. The "Select" button instead has "kentico.components.contentselector.dialog.button.apply" as its text. I've tried searching for this in a different branch of my code where it works, but I can't find where it is defined.

I have checked in CMSResources/CMS.resx and the Localisation application in the CMS

Is this a known issue with the latest hotfix?

Cheers, Danny

Recent Answers

David te Kloese answered on November 29, 2021 15:26

Can you check if you accidentally did something to:

..\App_Data\Global\Resources\Kentico.Components.resx

0 votesVote for this answer Mark as a Correct answer

Danny Winbourne answered on November 29, 2021 16:07

So, the entire "global/resources" folder was excluded for some reason (hence it not getting returned in searches). However, even after adding it back in, I am faced with the same issue. I also can't find these specific resource strings in these files.

I am using the following attributes in my properties file for the widget in question:

[EditingComponent(PageSelector.IDENTIFIER, Order = 100)]
[EditingComponentProperty(nameof(PageSelectorProperties.Label), "My Label")]

Maybe this has changed in V13?

0 votesVote for this answer Mark as a Correct answer

Danny Winbourne answered on November 29, 2021 16:07 (last edited on November 29, 2021 16:10)

None of these files were updated during the upgrade I should also add.

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on November 30, 2021 12:08

I would try clearing the cache. The resource strings are compiled into DLL and are part of Kentico.Content.Web.Mvc namespace. I would double check that the NuGet packages on the front end app were updated correctly and build the solution with no errors.

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on December 8, 2021 07:51

Just to update on this - there was the CMSDefaultUICulture web.config key in the MVC app specified for different culture - which caused the MVC app to look for the resx file in this culture, which did not exist. Removing the key from the MVC app's config fixed the missing resource string issue.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.