Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Yahoo.com no longer works with Foxfire 11

  • 3 replies
  • 5 have this problem
  • 1 view
  • Last reply by user633449

I did not keep a copy of 10 and now 11 does not allow yahoo.com to work. I want to go back to 10 as it did work but mozilla no longer shows where 10 is or any other apart from 11 which does not work.

I did not keep a copy of 10 and now 11 does not allow yahoo.com to work. I want to go back to 10 as it did work but mozilla no longer shows where 10 is or any other apart from 11 which does not work.

Chosen solution

Problem was doing two things at the same time. 1) update foxfire to 11. 2) add "RequestPolicy 0.5.25". 2a) Panic when the combination did not work (yet, need to understand "RequestPolicy"). 2b) Found foxfire 10 (was difficult), went back to 10, had same problem, removed "request policy", problem solved. 2c) went back to 11, with/without "RequestPolicy" enabled to identify problem.

Would have been easier if 10 was easily available. Thanks

Read this answer in context 👍 0

All Replies (3)

Please try reading this article: Websites look wrong, which may help yo bring yahoo back to how it should look for you.

Chosen Solution

Problem was doing two things at the same time. 1) update foxfire to 11. 2) add "RequestPolicy 0.5.25". 2a) Panic when the combination did not work (yet, need to understand "RequestPolicy"). 2b) Found foxfire 10 (was difficult), went back to 10, had same problem, removed "request policy", problem solved. 2c) went back to 11, with/without "RequestPolicy" enabled to identify problem.

Would have been easier if 10 was easily available. Thanks

The reason Firefox 10 is not made readily available is because there are some major security holes in it which have only been fixed in Firefox 11. When a new version of Firefox comes out (11 is this case) the one before is dropped from support. I'm glad you found out the problem though.