We’ve seen the following issues with Chrome 36 and Tridion 2011 and Tridion 2013:

  • Component presentations are not displayed when viewing a page in the CME.
  • Cannot create a new component.
  • HTTP details are not shown in Publication Targets.

The symptoms may include the message "xlink' is an undeclared prefix."

We've applied all the latest service packs and hotfixes, but still see these issues.

If you see other issues with Chrome 36, please add them as comments here.

  • 1
    I've also noticed that when creating/editing components (in CME) with lots of fields, the vertical scrolling on Chrome 36 doesn't work very well. I can only scroll down a little and therefore cannot see all the fields available. Commented Jul 18, 2014 at 13:55
  • Seems like the below error screen-shot belongs to this: !enter image description here (80040356) Unable to retrieve converted schema Error in line 73 position 306. 'EndElement' 'ItemFieldDefinitionData' from namespace 'sdltridion.com/ContentManager/R6' is not expected. Expecting element 'ExtensionXml | EmbeddedFields | EmbeddedSchema'. I have tried to create/modify a schema where I added one embedded schema field - As soon as I save or click on Source tab, it throws this error. Working fine in IE. Commented Jul 21, 2014 at 10:47
  • SDL have an open bug with Chromium here: code.google.com/p/chromium/issues/detail?id=390879 Commented Jul 21, 2014 at 12:49
  • All issues have been resolved in version 38 of Chrome browser. I did not apply any hotfixes in my SDL Tridion 2011 SP 1. Commented Nov 5, 2014 at 8:17

3 Answers 3


Just to update to help everyone; Following hot fixes has been released to fix this issue:

  • As far as we can see, chrome versions 37 and 38 still haven't fixed this, so I guess this hotfix will become "permanent".
    – Nuno Linhares
    Commented Jul 23, 2014 at 15:04
  • looks like Chrome is heading towards IE path Commented Jul 23, 2014 at 15:05
  • Well, IE has not broken a fundamental part of XML parsing... so I'm not sure that comparison is fair towards Microsoft. Can't believe I'm defending MS instead of Google.
    – Nuno Linhares
    Commented Jul 23, 2014 at 15:07
  • Just applied the hotfix on 2013 SP1 systems. Stuff works again!
    – Raimond
    Commented Jul 23, 2014 at 21:06

This appears to be due to a change (or defect) in how Chrome 36 handles the xlink namespace.

The Tridion vendor is working on a hotfix to adjust to the Chrome xlink handling - if I hear anything, I'll update here.

  • 1
    For the curious ones, this is the issue in question: code.google.com/p/chromium/issues/detail?id=390879, we're working double time to fix it ASAP.
    – Nuno Linhares
    Commented Jul 18, 2014 at 13:34
  • Mac Firefox version 30 fails to load the CMS UI. We are not seeing the authentication pop-up.
    – S. T.
    Commented Jul 18, 2014 at 19:06
  • 1
    not related to the original question, but don't see a way to delete my comment from this thread. Mac Firefox version 30 fails to load the CMS UI. We are not seeing the authentication pop-up. This is because NTLMv1 has been disabled by default developer.mozilla.org/en-US/Firefox/Releases/30/…
    – S. T.
    Commented Jul 18, 2014 at 19:18
  • That sounds like a different issue S.T.. You might want to open a separate question for it and provide the answer yourself. Commented Jul 19, 2014 at 17:39
  • Officially, FF on Mac is not supported (only Safari), which means it may not have been tested. And indeed it should be a different question rather than a comment here.
    – Nuno Linhares
    Commented Jul 21, 2014 at 10:19

If your system hasn't already "upgraded" to Chrome 36, you can stop automatic Google updates by following the instructions here.

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.