Posts

Showing posts from August, 2015

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   System.Number.ParseInt32(String s, NumberStyl…

RESOLVED: A domain specified in the Sitecore.Security.SwitchingProfileProvider provider/domain map could not be found. Domain name:

If you encounter the following error working with setting up Active Directory integration:

A domain specified in the Sitecore.Security.SwitchingProfileProvider provider/domain map could not be found. Domain name: <yourdomain>

Line 3897:        <clear />
Line 3898:        <add name="sql" type="System.Web.Profile.SqlProfileProvider" connectionStringName="core" applicationName="sitecore" />
Line 3899:        <add name="switcher" type="Sitecore.Security.SwitchingProfileProvider, Sitecore.Kernel" applicationName="sitecore" mappings="switchingProviders/profile"></add>
Line 3900:      </providers>
Line 3901:      <properties>


The solve is pretty simple, add a domain element with your domain name such as: <domain name="yourdomain" />  to App_Config/Security/Domains.config

RESOLVED: Solr Exceptions - Document contains at least one immense term in field

If you implemented Solr with Sitecore using Solr 5.x, you may run into the following error when indexing extremely large content in string fields:

org.apache.solr.common.SolrException: Exception writing document id <xxxuniqueid> to the index; possible analysis error. Caused by: java.lang.IllegalArgumentException: Document contains at least one immense term in field="<xxxfieldname>" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[10, 9, 9, 10, 32, 32, 32, 32, 32, 32, 82, 84, 82, 83, 32, 70, 97, 99, 105, 108, 105, 116, 121, 32, 10, 32, 32, 32, 32, 84]...', original message: bytes can be at most 32766 in length; got <intgreaterthan32766>Caused by: org.apache.lucene.util.BytesRefHash$MaxBytesLengthExceededException: bytes can be at most 32766 in length; got <intgreaterthan32766>

This is due to the fact that ther…

Sitecore: Indexing Associated Content

Setting up indexes and indexing content for site search in Sitecore is a pretty straightforward task and there is an extensive knowledge base put together by the community with various examples. One useful construct we often find ourselves implementing for keyword search is setting up a computed field. I typically use this construct to index any additional content referenced by a page, typically (content blocks, promos, callouts) added to the page via presentation details


The Need: Index externally reference content by a page itemSolve: Create a computed field to index TextField and HtmlText type fields of referenced items
This implementation fetches all the renderings for the current item's presentation for the default device and checks their datasource item for index-able content.
As a suggestion, check if the current item inherits from certain page templates else skip the execution.

Step1: Create a class and implemented the IComputedIndexField interface as shown below: public cl…