After updating to release 21.0, I'm no longer able to join an online meeting using Microsoft Lync 2010 if Firefox is set as my default browser.
After updating to release 21.0, I'm no longer able to join an online meeting using Microsoft Lync 2010 if Firefox is set as my default browser. I get prompted to "Join the meeting using your web browser" or "Download and install Lync Attendee". Neither option works. Joining using web browser results in a prompt to install missing plugins, but then no suitable plugins are found. Trying to install Lync Attendee fails because Lync 2010 is already installed.
I also tried installing Firefox beta release 22.0, but the issue remains.
Ñemoĩporã poravopyre
hello ScottRey, please try this: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named plugins.load_appdir_plugins. double-click it and change its value to true (a restart of the browser might be necessary afterwards for the change to take effect). some background on the issue is explained in http://www.ghacks.net/2013/05/15/why-you-may-have-lost-access-to-plugins-or-extensions-in-firefox-21/
Emoñe’ẽ ko mbohavái ejeregua reheve 👍 11Opaite Mbohovái (5)
Ñemoĩporã poravopyre
hello ScottRey, please try this: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named plugins.load_appdir_plugins. double-click it and change its value to true (a restart of the browser might be necessary afterwards for the change to take effect). some background on the issue is explained in http://www.ghacks.net/2013/05/15/why-you-may-have-lost-access-to-plugins-or-extensions-in-firefox-21/
Your suggestion worked like a charm, philipp. Thanks! And I appreciate that you provided a link to the background explanation.
great, thanks for reporting back!
I noticed that I can also move the "Plugins" folder into the "Browser" folder and it works. Is there a downside to doing this?
I suppose it might interfere with an uninstaller. Is that the reason you suggested the about:config approach?
yes, and also in restricted enterprise environments not everyone might have write access to the program folder...