search

valdisiljuconoks / localization-provider-opti

Database driven localization provider for Optimizely (ex. Episerver) websites
Apache License 2.0
11 stars 16 forks source link

Add localization provider after built-in providers #230

Open stefanolsen opened 2 weeks ago

stefanolsen commented 2 weeks ago

On a customer project, a Commerce solution, there was an issue where loading the editor UI issued thousands of SQL queries to get individual translation resources.

I found that ShellInitialization adds its EmbeddedXmlLocalizationProvider's to ProviderBasedLocalizationService, after the DbLocalizationProvider has added itself. So every time the UI needs an embedded resource, it will first attempt to load it from DbLocalizationProvider.

Would it be possible to add DbLocalizationProvider after EmbeddedXmlLocalizationProvider?

valdisiljuconoks commented 2 weeks ago

hey, this is the latest commerce, right?

stefanolsen commented 2 weeks ago

These are some of the package versions I am currently using: