Loaded unexpected element while trying to get rendering html from server. Expecting last tag to be closing script marker

If you have googled this error before, the most promising result is this article. Now this article does a good job of explaining what <code> elements are to the page-editor and their connection with this error and also proposes a solution that may or may not be the cause of the issue, in my case it wasn't.

Here is what my issue was:
  1. Working with Sitecore MVC view renderings
  2. A page has view renderings within nested placeholders, e.g. a hero slide item added to a hero slide item container with a placeholder (say hero-container), which in turn is added to the body of the page using another placeholder (say main-content).
  3. Using page editor, tried adding a new component to the leaf placeholder (say hero-container), and got the first popup for the allowed controls (if the field is populated)
  4. Once the component is selected and clicked Ok, nothing happens. Looking at the console I saw the following:

(I recommend you click on the link to the .js file and checkout the code to see exactly what the page-editor is looking for and how those <code> elements are being parsed.)

So, after spending a few hours and comparing components that worked with the ones that did not work in the page editor with similar nesting of placeholders, I found out that there is an easy work around. All you need to do is populate the "Datasource Location" field on the component and voila!! everything works. It's still a workaround and I am looking to create a ticket for Sitecore to look into this issue. Let me know if this worked for you or if you found other fixes or patches from Sitecore for this issue.





Comments

Post a Comment

Popular posts from this blog

Is Rendered Item Valid XHtml Document Could not find schema information warnings during publish item Sitecore 7.2

Image
Note: Since we now live in the HTML5 world, the simple resolution to any XHtml validation errors is to remove the XHtml validation rules on  System->Settings->Validation Rules->Global Rules item. Sitecore should update it's validation rules to be relevant to HTML5. This make the rest of this post obsolete :). I created a simple approval workflow in Sitecore 7.5 and tried to approve an item for publishing and found a bunch of validation errors in the Validation Results. Most of them were related to the "Is Rendered Item Valid XHtml Document" section which looked like this: The problems were related to violations of the W3C HTML5 recommendation An important note here is: The element containing the character encoding declaration must be serialized completely within the first 1024 bytes of the document. Adding the following xmlns attribute to the Html tag fixed most of the errors: <html lang="en" xmlns="http://www.w3.org/1999/
Read more

Sitecore Tabbed Select Rendering dialog

Image
If you aren't already doing this, you should be! Found an interesting module (unable to find it on Sitecore Marketplace) to show renderings grouped into tabs while using the Select Rendering dialog from page editor. The idea is to go from this: To: The approach is promising with a few updates: Tried implementing it by inheriting from SelectRenderingForm and it did not work. No rendering items were being listed. Had to decompile Sitecore.Client.dll and copy the code from Sitecore.Shell.Applications.Dialogs.SelectRendering.SelectRenderingForm Had to comment the following line in OnLoad  this.Renderings.InnerHtml = this.RenderPreviews((IEnumerable<Item>)renderingOptions.Items); Found a few issues with the styles, could have be an updated style sheet for Sitecore 7.5, but had to add the following attributes to the tabstrip Background="white" Padding="0px" style="position:absolute; width:100%;top:0px" Here is a detailed description of my implementati
Read more

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 fa
Read more