Posts

Showing posts with the label Sitecore 8

SOLVED: ERROR Rendering control not found for Item in Sitecore

A simple solution (maybe too obvious to some) to a rather cryptic error. This error occurs if you use a MVC rendering (.cshtml or controller rendering) on a page whose Layout item points to a .aspx file. As in, make sure you have a MVC layout when adding MVC renderings to a page. Duh!

ISSUE:Sitecore 8 Edit Frame does not display fields for the context language

SOLVE: Sitecore provided a patch to fix the issue:  https://kb.sitecore.net/articles/814090

RESOLVED: Connection error to search provider [Solr] : Unable to connect to , Core: [index_name]

If you are working with Solr provider for Sitecore 8, I'm sure you have already read this  article regarding changes to the Schema.xml that must be applied. In a recent Solr integration with Sitecore 8 Update 5  (rev. 150812) , I ran into the following error(s): Connection error to search provider [Solr] : Unable to connect to <solr service address>, Core: [index_name] Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: Sitecore.ContentSearch.Exceptions.SearchProviderConnectionException: Connection error to search provider [Solr] : Unable to connect to [http://ocomp-sc-solr:8080/solr], Core: [social_messages_master] Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can ...

BUG: $now in Standard Values changes to 1/1/0001 on Save

Working with Sitecore 8 Update 3 (rev. 150427) I ran into a bug where $now, $date and $time tokens don't seem to be working correctly in Standard Values. Reported it to Sitecore and they confirmed it as a bug and provided the following workaround: BUG: Adding $now to Standard Values of a template and saving changes the value to 1/1/0001 SOLVE: While on the Standard Values, check "Raw Values" under the View tab. Then add the $now token and Save. Un-check the Raw Values and you will still see a 1/1/0001 value in Standard Values but each time a new item is created, it will have the correct DateTime value. This should with with $date and $time tokens as well.

RESOLVED: Upload file to Sitecore 8 Media Library causes Input string was not in a correct format error

Apparently there is a bug in Sitecore 8 Update 3 (rev. 150427), when you try to upload a file that is 0 Bytes in length, you get the below exception: Server Error in '/' Application. Input string was not in a correct format . Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.  Exception Details: System.FormatException: Input string was not in a correct format. Source Error:  An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [FormatException: Input string was not in a correct format.]    System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +14292453   ...