Earlier I wrote that turning on NPAPI plugin support to Chrome is a kind of task for "power users". I have found some instructions how to do it and perhaps it is not that bad. If using Java is still critical, you can give your users short and clear instructions. Which ones?
If you update your Chrome to the version 42, you will discover that the browser no longer displays a Java applet. The NPAPI plugin support is phased out in accordance to their plan as I wrote earlier.
We started new year with a new feature - an ability to upload entire folders with HTML5 uploader. What is important to know if this feature is critical for you?
In the end of 2014, Google updated their plans to phase out NPAPI (and, therefore, Java) support. In short, we have one more quarter to prepare. Let's elaborate.
Since the date of Java shutdown in Chrome is approaching, I would like to write a review of Java uploader vs. its HTML5 counterpart. What features you will lose if you switch from Java to HTML5? Are they critical? Let's try to figure out.
About one year ago Google announced that they want to clean up Chrome from 90es legacy and remove NPAPI support (and, therefore, get rid of Java plugin). The transitional period is about to finish. What it means for Aurigma's Java uploader?
Today we released new Image Uploader 7.0.28. It includes long list of improvements and bug fixes