Howdy all!
Today I was approached by several people wondering why MyVMK was no longer running in their Chrome browser. I initially chalked it up to a faulty cache but this wasn't the case. There was an update rolled out yesterday and today and I have good and bad news.
First the good news. You can fix this issue right now:
1) In Chrome, go to chrome://flags/#enable-npapi
2) You will see a section called "Enable NPAPI" and there should be a link to "Enable" it.
3) Click the Enable link.
4) Restart your computer. Yes, completely restart.
5) Enjoy MyVMK in your Chrome browser again.
And now for the sad news...
This fix is only temporary. In the current version of Chrome (42.x) we have the NPAPI option to enable NPAPI plugins. However, Chrome will eventually not be supporting NPAPI plugins like Shockwave. It will stop allowing them. Google is asking developers to start using secure PPAPI / Pepper plugins as well as HTML5.
What this means...
I believe that myVMK will eventually have to move to a new interface. I've seen threads where Amy is testing a new one and that looks promising. However, for Chrome users -- the end is near. And I believe myVmk Pal is using the Awesomium browser which is a subsection of the Chromium project. I'd bet that is going to stop working soon if it hasn't already.
Feel free to ask any questions.
Edit: For any other techies like me out there you can read the Chromium Blog which explains Google's decision. http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
Today I was approached by several people wondering why MyVMK was no longer running in their Chrome browser. I initially chalked it up to a faulty cache but this wasn't the case. There was an update rolled out yesterday and today and I have good and bad news.
First the good news. You can fix this issue right now:
1) In Chrome, go to chrome://flags/#enable-npapi
2) You will see a section called "Enable NPAPI" and there should be a link to "Enable" it.
3) Click the Enable link.
4) Restart your computer. Yes, completely restart.
5) Enjoy MyVMK in your Chrome browser again.
And now for the sad news...
This fix is only temporary. In the current version of Chrome (42.x) we have the NPAPI option to enable NPAPI plugins. However, Chrome will eventually not be supporting NPAPI plugins like Shockwave. It will stop allowing them. Google is asking developers to start using secure PPAPI / Pepper plugins as well as HTML5.
What this means...
I believe that myVMK will eventually have to move to a new interface. I've seen threads where Amy is testing a new one and that looks promising. However, for Chrome users -- the end is near. And I believe myVmk Pal is using the Awesomium browser which is a subsection of the Chromium project. I'd bet that is going to stop working soon if it hasn't already.
Feel free to ask any questions.
Edit: For any other techies like me out there you can read the Chromium Blog which explains Google's decision. http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
Last edited: