16

Is anyone else experiencing issues with Chrome 42 upgrade and Tridion?

I have 2 users who upgraded to Chrome 42 and are now getting the "Failed to open a window. If you have a pop up blocker enabled, disable it." message when trying to open an inherited component. Opening the at the source / local publication level opens fine.

We are using SDL Tridion 2013 SP1 HR1.

I have tried to submit a ticket at on the support portal but am getting a 504 Gateway time-out error. Perhaps everyone is at SDL Innovate this week.

7

As promised, I have applied Hotfix CME_2013.1.1.88718 to our environments and it has fixed the Chrome 42 issue on all of them.

Hotfix is available from SDL support or https://www.sdltridionworld.com/downloads/hotfixes/SDL_Tridion_2013_SP1_HR1/index.aspx

Good luck to everyone else who had this problem and thank you for the responses.

| improve this answer | |
4

Yes - I have experienced this problem, and have also heard reports from other people of the same thing. I've been working around it by simply using a different browser. It's starting to look like Chrome updates are a source of risk. Do you remember the problems with Chrome 36? That problem was addressed in the short term by a Tridion hotfix, and then eventually by a fix in Chrome. So it would make sense to report this via Tridion support.

| improve this answer | |
  • And let's hope the portal comes back up soon. – Dominic Cronin Apr 20 '15 at 10:57
  • Hi Dominic, Thanks for your response. I do remember the Chrome 36 issues vividly. I'm glad it's not just us then. I have managed to get a support ticket raised and will update this thread when I get a response. – Steve Redgewell Apr 20 '15 at 11:16
  • 1
    We are also facing the same issue. Hope to see quick resolution on this as the impact is widespread. Can this be added to Tridion KB in known issues as it helps in keeping watch on issues which impacts us and equips us to better communicate with our users when they face these issues? – Vipin Kothari Apr 20 '15 at 22:40
  • Another one suffering this issue. – Raúl Escudero Apr 21 '15 at 9:07
  • Rest assured that SDL is looking into it. Hopefully we'll have a hotfix for you soon. – Peter Kjaer Apr 21 '15 at 9:21
1

The hotfix for this issue is available on Tridion World on the downloads page for 2013 SP1 HR1 - CME_2013.1.1.88718: https://www.sdltridionworld.com/downloads/hotfixes/SDL_Tridion_2013_SP1_HR1/index.aspx

| improve this answer | |
1

Although the hotfix - CME_2013.1.1.88718 has been released for SDL Tridion 2013 SP1 HR#1; but I can confirm that this will also work for SDL Tridion SP1 as well. Apply the hotfix on my SDL Tridion 2013 SP1 environment and it is working fine.

| improve this answer | |
0

SDL sent CME_2013.1.1.88718 today, that they said would resolve this issue.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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