A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
AI OnAI Off
A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
Thank you for reporting this, sounds like a bug to me, we will have a look.
Case:
* resource does not exist in langugage "en"
* site is configured to use fallback mode in localization providers
* fallback culture - "en".
* Visitor is browsing site in "en" culture.
For single call of the LocalizationService.GetString("...") underlying list of providers are called twice - one for the language visitor is currently using("en"), second call for the fallback language - "en" again.
Does it make sense to call GetString() for the same culture as defined fallback culture if localization service already knows that resource does not exist for that langauge?