On Tridion 2013 SP1 and 2011 SP1, after I upgraded Google Chrome browser version to 49.0.2623.75, a component which includes component link or multimedia link field cannot be saved.

When creating a new component, I selected a linked component at component link field and click 'save and close' button. Then the component wasn't saved and following error occured

Uncaught TypeError: Cannot read property 'console' of null

enter image description here

Does anyone know same problem? Is it possible to avoid this problem by changing browser setting, or is it a Tridion's defect?


  • We're looking at it. As soon as we understand what did Google break, we'll fix it. This also affects Web 8.
    – Nuno Linhares
    Commented Mar 8, 2016 at 8:21
  • And to answer your 2nd question: if it works in every other browser, and in the previous versions of Chrome, it's probably not a Tridion defect. Chrome introduces breaking issues quite regularly, in Chrome 36 (or around that) they had a similar issue that got fixed a couple of versions later.
    – Nuno Linhares
    Commented Mar 8, 2016 at 8:42
  • Hofixes available now
    – Raj Kumar
    Commented Mar 15, 2016 at 9:31
  • Please refer below Answer tridion.stackexchange.com/questions/14200/… Commented Mar 17, 2016 at 6:32

3 Answers 3


Lots of users including me facing issue with mentioned version of chrome.

Hot Fixes available now. Login to SDL Tridion World required before downloading.

SDL Tridion 2011 SP1 HR2: Hotfix CME_2011.1.2.1673

SDL Tridion 2013 SP1 HR1: Hotfix CME_2013.1.1.1673 (Updated version available now)

  • 1
    The above Hotfix Hotfix CME_2013.1.1.1673 is not working for chrome Version 49.0.2623.87 . Commented Mar 16, 2016 at 11:07
  • working for me in above browser in 2013 sp1 hr1, , make sure you updated sytem.config and try clearing your browser cache
    – Raj Kumar
    Commented Mar 16, 2016 at 15:59
  • earlier version which i installed has only tree.js it worked for me. i think now it has been updated without even changing the version name :( try it now.
    – Raj Kumar
    Commented Mar 17, 2016 at 4:18
  • There were two versions of the hotfix released, the first version only tree.js file was included and in next version (with the same hotfix number) it included two files: tree.js and FormatArea.js. it is working post apply latest version with FormatArea.js and tree.js Commented Mar 17, 2016 at 6:29
  • @Rameshponna yes you are right and that's what i wrote in my last comment.
    – Raj Kumar
    Commented Mar 17, 2016 at 6:32

This is a known issue to SDL. I understand they are working on a fix ASAP.


If your copy of Chrome hasn't already updated itself, this may help:



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.