Activities of "fjinc"

Hi We're trying to hide certain localisations from the users in the frontend and ran into a problem and the eventual cause seems to be the ExternalLocalizationStore service not deleting old localisations from the ExternalLocalizationStore table. We found this out after we deployed a fix to our staging environment that removed a localization key value - however this did not get propagated to the database or the api/abp/application-localization api, meaning we could see the value we wanted to removed in the response.
I have solved this by disabling the ExternalStore feature and deleting the values from the AbpLocalizationTexts database table however this isn't ideal as it means we no longer have the ability to edit the localizations using the Language Management UI (since our localisations are distributed across different webhosts). There is a similar problem with the AbpLocalizationResources table where the resource does not get removed if you delete it from the application altogether.

Steps:

• Create a localization resource in your application with some en.json
• Run the host and ensure AbpExternalLocalizationOptions.SaveToExternalStore is set to true in the host configuration.
• Observe the resource and the values from your en.json gets added to the AbpLocalizationTexts table
• Remove several keys from the en.json file
• Rerun the host (ensure db is kept online to simulate prod/stg environment).
• Observe the entry in AbpLocalizationTexts table still shows the keys you have just deleted.
• This can also be checked by looking at the LanguageManagement UI and seeing the value there still. I have cleared redis to ensure I'm not seeing old cached values and I can see they get repopulated upon page refresh so it isn't this.

If this is the intended behaviour and just requires manual patching each time we make changes to the .json files it is disappointing as it adds additional overhead to deployments. Is there a fix for this that deletes older keys from the db to ensure only the latest is shown to the users? We are using ABP commercial 7.3.3. Thank you ! :)

• ABP Framework version: v7.3.0 - replicable on ABP demo on 7th June 2023.
• UI type: Angular
• DB provider: Unknown
• Tiered (MVC) or Identity Server Separated (Angular): Unknown
• Steps to reproduce the issue:
  • Login as admin
  • Navigate to Saas -> Tenants -> Users
  • Select Actions -> "Login with this tenant" for any tenant
  • Login as 'admin' tenant user
  • Console throws following error: ERROR Error: Uncaught (in promise): Wrong nonce: undefined
• Expected behaviour: No console error is thrown
• Actual behaviour: Console error is thrown
• Further issues:
  • No impact on the tenant impersonation functionality.
  • Throws error again when returning to the host account from the impersonated tenant user.
  • Seem to throws error after the impersonation action as user is redirected before error is thrown: