New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lazy-load the ProviderResolver #11

GreyGhostStudio opened this Issue Nov 13, 2014 · 0 comments


None yet
1 participant
Copy link

GreyGhostStudio commented Nov 13, 2014

Just dropping in the bug we noticed around Synthesis in a production CD environment with the master db and master indexes removed.

"FieldNameTranslator is only used during generation and thus should not need to be changed in CD, but does as it currently stands due to the eager dependency resolution."

Here is the exception we were seeing:

4244 16:57:25 ERROR Error Initializing ProjectA.Model.Custom.CurrentPageBaseModel
Exception: System.TypeInitializationException
Message: The type initializer for 'Synthesis.Initializers' threw an exception.
Source: Synthesis
at Synthesis.ItemExtensions.As[TTemplate](Item item)
at ProjectA.Model.Custom.CurrentPageBaseModel.Initialize(Rendering rendering) in d:\Websites\ProjectA\ProjectA.Model\Custom\CurrentPageBaseModel.cs:line 15

Nested Exception

Exception: System.ArgumentException
Message: Index sitecore_master_index was not found
Source: Sitecore.ContentSearch
at Sitecore.ContentSearch.ContentSearchManager.GetIndex(String name)
at Synthesis.Configuration.ProviderResolver.LoadFieldNameTranslatorFromConfig()
at Synthesis.Configuration.ProviderResolver..ctor()
at Synthesis.Configuration.ProviderResolver.get_Current()
at Synthesis.Initializers..cctor()

Switching this value removed the errors:

Setting: indexConfiguration name="sitecore_web_index"

@kamsar kamsar closed this in 7b7b913 Nov 16, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment