I work for User Testing, which uses a Java-based screen recorder to make videos of people using commercial websites and offering spoken feedback on the site. Since instal… (Lesen Sie mehr)
I work for User Testing, which uses a Java-based screen recorder to make videos of people using commercial websites and offering spoken feedback on the site. Since installing the Java 1.6.0_33 update for Snow Leopard on my MacBook, the User Testing screen recorder does not recognize that Java is installed, and won't work.
If I switch to Chrome, all works smoothly. I have the latest version of Firefox, and have installed the latest updates. I have opened Java Preferences in my Utilities, and made sure that the checkbox "Enable applet plug-in and Web Start applications" is checked. I have cleared the cache and cookies in Firefox. The problem still persists.
User Testing says no other Mac users have reported the problem, and so they cannot help me. I rely on a Firefox add-on that is not available for Chrome to notify me of new User Testing jobs (which are normally claimed in seconds), so it is not practical for me to simply switch to Chrome or another browser.
Interestingly, when checking my plugins in order to fill out the information required below in this help request, I was sent to a Firefox page that says "For your safety, Firefox has disabled your outdated version of Java. Please upgrade to the latest version."
When I click the link, it says that Apple supplies its own version of Java, which of course I have already installed. Guess this is the root of the problem, but how do I fix it?
EDITED TO ADD SOLUTION:
After even more Googling, I eventually stumbled on the solution. In the Firefox menu, I chose Help>Troubleshooting Information, and clicked "Show in Finder" under Application Basics. I then quit Firefox, clicked on the Profile folder, deleted the file "pluginreg.dat", and restarted Firefox. Java now shows up among my plugins, and is enabled by default. The failure of pluginreg.dat to update automatically was supposed to be an old Firefox problem that has been solved, but apparently that is not always the case.
Thank you to everyone who answered.