IBM Connections in combination with Chrome version 60


Update 17-08-17

IBM PMR update

“thank you very much for your update. It will be an ifix for IBM Connections but unfortunately we did not have any information about an ETA Date.
The priority is high as many customers reported this problem.

I will check the status for the defect and the technote for any update and keep you informed.”

TechNote -> http://www-01.ibm.com/support/docview.wss?uid=swg22007236&myns=swglotus&mynp=OCSSYGQH&mync=R&cm_sp=swglotus-_-OCSSYGQH-_-R

 


Since the update to Chrome version 60 we started to notice that some

of the functionality of IBM Connections breaks when using it with the Google browser.

Until so far we have found three items of IBM Connections which no longer work
with Chrome version 60.

  • Creating a Community event doesn’t work.
  • Content in the Events widget on the Homepage isn’t always displayed correctly.
    ( An error occurred while displaying content. Contact your system administrator. )
  • Placing a comment on status update in the ActivityStream doesn’t work.
    ( This goes for the ActivityStream on the Homepage and for
    the “Recent Updates” stream on a Profile page.
    When performing the same action in the popout window it works okay. )

We see that it happens with IBM Connections 5.0 CR4, 5.5 CR3 and with 6.0.

Related to these issues we raised two PMR’s. If you want to increase the weight of your
PMR’s you could refer to these two.

28607,211,788 – IBM Connections 5.5 – Chrome version > 60 Creating events.

28593,211,788 – IBM Connections 5.5 – Chrome 60 causes problems commenting in IBM Connections

Below some screenshots of the issues we see.

Creating a Community event doesn’t work

 

 

Content in the Events widget on the Homepage isn’t always displayed correctly.

Placing a comment on status update in the ActivityStream doesn’t work

 

 

This entry was posted in ibm connections and tagged , , , . Bookmark the permalink.

One Response to IBM Connections in combination with Chrome version 60

  1. Nicki says:

    We had noticed this immediately after the Chrome update to v60. I opened a PMR and am told that IBM is working with Google to get this resolved. Hopefully this will be fixed soon, but in the meantime we are asking folks to use another browser as a workaround.

Leave a Reply

Your email address will not be published. Required fields are marked *

Please leave these two fields as-is:

Protected by Invisible Defender. Showed 403 to 801,095 bad guys.