0

When editing pages in EE using Chrome, clicking on fields show the field details popup but with a '[Not set]' title enter image description here whereas in Firefox it shows the actual field name:

We're using Sitecore 8.1 (rev. 160519)

4
  • any browser console error or entries in chrome ? Feb 21, 2017 at 11:58
  • Errors, no. But warnings that don't seem related: "SessionTimeout not found in settings scForm.Settings", "ApplicationCache is not declared", "Synchronous XMLHttpRequest on the main thread is deprecated...", "Use of the Application Cache is deprecated..."
    – TamerM
    Feb 21, 2017 at 12:14
  • please make sure you have same URL parameters in two browsers like sc_site=<sitename>&sc_db=master&sc_lang=<language>&sc_version=<NUMBER> Feb 21, 2017 at 13:04
  • I copied and pasted it from one browser to the other
    – TamerM
    Feb 21, 2017 at 14:28

2 Answers 2

1

Please download the following Sitecore Support Patch here.

It is a fix about the Field Editor dialog has no header. If the patch does work, I would recommend you to contact Sitecore Support and ask them one which is compatible with your version.

As a side note, Sitecore responded that the patch is compatible with both Sitecore version 8.1 and 8.2.

The Sitecore Patch detail is: Sitecore.Support.1017770. The zip file contains an assembly and a config file.

  1. Place the attached Sitecore.Support.101770.config file to the \App_Config\Include folder.

  2. Place the attached Sitecore.Support.101770.dll assembly to the \bin folder.

4
  • the issue was occurring only in chrome browser. is patch for chrome browser issue ? Feb 21, 2017 at 16:12
  • Not sure if it is for browser specific. I need to check this the team. But we were faced with the same issue. Feb 21, 2017 at 16:27
  • @HishaamNamooya, thank you but this did not work... Could it a version issue?
    – TamerM
    Feb 22, 2017 at 9:57
  • 1
    It might be. I would suggest to create a support ticket at sitecore. Feb 22, 2017 at 10:06
1

This turned out to be a js compatibility issue. Our site uses hyphenator.js library which conflicted with the Sitecore's EE elements. I updated the hyphenator.js file to exclude scChromeData and scWebEditInput classes from its processing logic and this solved the issue.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.