Skip to content
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

Synthesis and SOLR - ArgumentNullException #34

Closed
zimpy opened this issue Sep 12, 2016 · 4 comments
Closed

Synthesis and SOLR - ArgumentNullException #34

zimpy opened this issue Sep 12, 2016 · 4 comments

Comments

@zimpy
Copy link

zimpy commented Sep 12, 2016

When requesting /synthesis.aspx it throws this exception. Unfortunately I don't have some steps to reproduce:

[ArgumentNullException: Value cannot be null. Parameter name: fieldTypeName] Sitecore.Diagnostics.Assert.ArgumentNotNull(Object argument, String argumentName) +63 Sitecore.ContentSearch.SolrProvider.SolrFieldMap.GetFieldConfigurationByFieldTypeName(String fieldTypeName) +40 Sitecore.ContentSearch.SolrProvider.SolrFieldNameTranslator.ProcessFieldName(String fieldName, Type returnType, CultureInfo culture, String returnTypeString, Boolean aggressiveResolver) +1319 Sitecore.ContentSearch.SolrProvider.SolrFieldNameTranslator.GetIndexFieldName(String fieldName) +31 Synthesis.Generation.MetadataGenerator.GenerateMetadata() +868 Synthesis.SynthesisHelper.ExecMetadataWithAutoFriending(IEnumerable1 configurations, Action2 processAction) +467 Synthesis.SynthesisHelper.CheckSyncAll() +181 Synthesis.ControlPanel.ControlPanelPipelineProcessor.CreateSyncSummary() +110

@zimpy
Copy link
Author

zimpy commented Sep 14, 2016

It seems like this happened because i didn't have any fields on my template. It only had some base templates. When i added a field directly on it, it worked.

@kamsar kamsar added the bug label Sep 22, 2016
@kamsar
Copy link
Collaborator

kamsar commented Sep 22, 2016

As a longer term enhancement, Synthesis really should modularize the content search stuff out of the core and into Lucene and Solr specific packages. Or maybe a shorter term one, if I can find the time (what's spare time again?)

@kamsar
Copy link
Collaborator

kamsar commented Oct 20, 2016

This isn't a complete fix but 306aac5 makes it not error (and generated no [IndexField] when the Solr name translator fails), as well as the option to disable content search integration entirely. This is in 8.2.2-RC01 on NuGet.

@kamsar
Copy link
Collaborator

kamsar commented Nov 18, 2016

This is fixed in 8.2.2 with an improved method from RC01

@kamsar kamsar closed this as completed Nov 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants