How to fix problems with Cox webmail after latest firefox update
Firefox auto-updated [55.0.3 (32-bit)]. Now some of my cox webmail page functions [delete, etc] stop working if I "leave" the Cox webmail page to go to any other page and then return to the webmail page. To get all the functions to work, I have to reload the webmail page [each time that I have gone to another page]. I have already tried resetting Firefox to its defaults. And temporarily disabling all of the plug-ins that firefox showed me. But neither of those two things fixed the problem. I tried contacting Cox, but there support staff was not able to fix the problem either.
Gekozen oplossing
FredMcD: Thank you for taking the time to post regarding my problem. Starting Firefox in Safe Mode did not solve the problem. Firefox blocked access to Shockwave Flash 20.0 r0, including not allowing any updating of it [due to security concerns]. [That Shockwave Flash version also did not show, at least as such, in my list of programs in Control Panel]. Your posts did set me off in another direction: namely having more than one version of a program at the same time. Even though Firefox told me [within the currently updated version] that it was updated/and except for the webmail issue seemed to be working fine/etc, I decided to add another current updated version of Firefox. The "second" copy of Firefox did not have the issue, while the "original" copy of Firefox continued to have it. I uninstalled the "original" Firefox, kept the "second" copy, and problem [at least for now, apparently] solved. Frankly, I am embarrassed that I did not think of/try this approach before. [And before I contacted Cox, searched through Mozilla's help sections, etc including posting here]. Again, thank you for your efforts, and for getting me to think in a direction that seems to have solved the problem.
Dit antwoord in context lezen 👍 0Alle antwoorden (4)
Separate Issue; Your System Details shows;
Installed Plug-ins
Shockwave Flash 20.0 r0
Shockwave Flash 26.0 r0
Having more than one version of a program may cause issues.
You must remove the older programs. Then get the current full installer.
Flash: Grab the uninstaller from here:
http://helpx.adobe.com/flash-player/kb/uninstall-flash-player-windows.html Uninstall Flash Player | Windows
http://helpx.adobe.com/flash-player/kb/uninstall-flash-player-mac-os.html Uninstall Flash Player | Mac
Then reinstall the latest version.
Note: Windows users should download the active_x for Internet Explorer. and the plugin for Plugin-based browsers (like Firefox).
Note: Windows 8 and Windows 10 have built-in flash players and Adobe will cause a conflict. Install the plugin only. Not the active_x.
Flash Player Version 26.0.0.151
https://get.adobe.com/flashplayer/ Direct link scans current system and browser Note: Other software is offered in the download. <Windows Only>
https://get.adobe.com/flashplayer/otherversions/ Step 1: Select Operating System Step 2: Select A Version (Firefox, Win IE . . . .) Note: Other software is offered in the download. <Windows Only>
See if there are updates for your graphics drivers https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration
Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.
A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?
Gekozen oplossing
FredMcD: Thank you for taking the time to post regarding my problem. Starting Firefox in Safe Mode did not solve the problem. Firefox blocked access to Shockwave Flash 20.0 r0, including not allowing any updating of it [due to security concerns]. [That Shockwave Flash version also did not show, at least as such, in my list of programs in Control Panel]. Your posts did set me off in another direction: namely having more than one version of a program at the same time. Even though Firefox told me [within the currently updated version] that it was updated/and except for the webmail issue seemed to be working fine/etc, I decided to add another current updated version of Firefox. The "second" copy of Firefox did not have the issue, while the "original" copy of Firefox continued to have it. I uninstalled the "original" Firefox, kept the "second" copy, and problem [at least for now, apparently] solved. Frankly, I am embarrassed that I did not think of/try this approach before. [And before I contacted Cox, searched through Mozilla's help sections, etc including posting here]. Again, thank you for your efforts, and for getting me to think in a direction that seems to have solved the problem.
That was very good work. Well done. Please flag your last post as Solved Problem so others will know.