So, with Java update 45, Ephox fails to load (it gets stuck at 53% when clicking on Design or Code View). This is apparently the case in IE 10 (Windows) and Safari (Mac). Anyone else have a similar issue?
Needless to say, people can’t edit content… (am about to file a TS ticket)
http://ephox.com/editlive/demo appears to work after accepting a couple of popup warnings.
I’m stuck with ephox on 67% with Safari 6.0.5 on OSX 10.7.5 with Java update 45
I am stuck at 59% on Firefox after Java update 45
Just did a roll back on the Java version for both the 32bit and 64bit version, and that resolved the issue.
Looks like it doesn’t work with Firefox on Windows 7 and Windows 8 (both Firefox and Internet Explorer).
Yup, a roll back to Java 7 u 25 (which appears to be the only one available in the Oracle archives) temporarily solves the issue. I say temporarily for obvious reasons of using an old release of Java…
To fix the issue please downgrade from Java7u45 as EditLive has significant issue with this version. Following is the Ephox support response for this issue:
Java7 update 45 is having significant issues with EditLive!
At this point we recommend that you downgrade your Java version and load EditLive ! again.
Yes, we’re seeing the same. I’ve recommended the roll-back to 7u25.
Technically, you can get Java 7 u 40 from the oracle network. While they haven’t yet put it up on the archives page, http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html the URL to update 40 follow a similar download path as to the ones listed in the archives…
List of vulnerabilities with Java 7 u 40 (That Java 7 u 45, which we can’t use, fixes):
http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html#AppendixJAVA
Hi folks - Was wondering if anyone had seen a weird issue with the ePhox applet not being loaded in IE/Chrome but being fine in Firefox.
It just started to happen today, which coincides with a message from Java to install 1.7.0 u45 JRE, I backed out of installing this, but could there be any way this would have affected the secuirty settings of the Applet. I’m saying that, as in the Java Trace console I can see network: Created version ID 1.7.0.40 and then network: Created version ID 1.7.0.45, so am wondering whether there is something in the JRE that stops it from working in IE / Chrome when an update is available?
Any help is much appreciated.
Thanks,
Bal
FYI, we are having to set Java Security to “Medium” as opposed to the default “High” in order for inline templates to work on the older version of Java.
From looking through the Java forums - it seems as if the applets will still check against the Java Security baseline which is now 7 u 45 - as outlined here:
I’m still on 7 u 40 and it has stopped working - so will try and change my security settings next…
Here is the latest from ephox about the Edit Live version 8 issue. As soon as they have a fix we can start working on the patch for 7.2. The 7.3 patch in QA updates EditLive in 7.3 to version 9 - which does not have the hanging issue.
-n
Michael Fromin (Ephox Support)
Oct 18 08:46 am (MDT)Mythili -
We are actively working with Oracle on this issue - but I cannot give you an estimate as we don’t know at present why EditLive is having these issues.
At present the workaround to get EditLive 8 working is as follows:
Downgrade the JRE to an earlier release of 1.7
Modify the Security Level (on the Security tab of the Java Control Panel) to Medium
At this point EditLive 8 should work properly. We apologize for this inconvenience and are working as fast as we can to address this issue.Michael Fromin
Director of Client Services
Ephox
Does this apply for Mac OSX as well? According to java.com (http://www.java.com/en/download/faq/java_mac.xml) you cannot rollback to 7u25 for OSX.
Based on that Oracle page, it looks like you would need to rollback to Java 6 on the Mac. http://support.apple.com/kb/HT5559?viewlocale=en_US.
Is it the case that a sensible fix is likely to be to upgrade from 7.2 to 7.3, once the forthcoming patch is available? That should resolve the issue by switching to Ephox 9?
Thanks
We have successfully installed Java 7 u 40 (and 25). You just need to follow the directions to remove the current version of Java and then download the previous version from the oracle archives…
For a mac, use: http://www.java.com/en/download/help/mac_uninstall_java.xml
Then download and install either update 25 or 40.
We have directions available to our users (It would be nice if Percussion had released something similar). Please note that we are restricting the download of the JRE just to our users: http://www.ensemble.cms.vt.edu/troubleshooting/java/java-revert-to-previous-version.html (So you may want to download the jres from the oracle archives and then make it available to your users)
In addition to my previous question on going to 7.3, can anyone clarify why (until a more permanent solution is in place) a switch back to Java 1.7.25 and not 1.7.40? Are issues definitely worse with 40? Clearly the more recent the Java the better.
Thanks
Yes upgrading to 7.3 would make sense as you will get Ephox 9 in the patch that was just released.
Oracle has really made a mess with these updates:
The current Java SE archive page now seems to only list update 25 and earlier as a download option, I don’t know if they are doing some “smart” client side detection of the version of Java installed when the list it built or what:
http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html
I can say that Java 1.7 update 17 works with all versions of the product. Deploying later versions for security updates makes sense, but if you just need stable Rhythmyx, that would be the update to take, pending patches for your release version or upgrading to 7.3.
We are currently waiting for a schedule on what additional Patches we can expect from Engineering.
Java update 40 and update 25 do seem to both work ok for most customers, but I have heard feedback from at least one customer that they had quirks with both update levels on certain client OS / browser combinations.
-n
[QUOTE=drossall;20992]In addition to my previous question on going to 7.3, can anyone clarify why (until a more permanent solution is in place) a switch back to Java 1.7.25 and not 1.7.40? Are issues definitely worse with 40? Clearly the more recent the Java the better.
Thanks[/QUOTE]
Thanks, although we’ve got extra constraints on JRE versions from this thread.
We’ll start planning on an upgrade.