Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ابحث في الدعم

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

Latest Headlines fails to load, any suggestions?

  • 6 ردود
  • 62 have this problem
  • 5 views
  • آخر ردّ كتبه jakem_

more options

About a week after updating to Firefox 6.o.2, Latest Headlines [Live Bookmarks feed to BBC ] quit loading. Any suggestions? Thanks, Bridgid.

About a week after updating to Firefox 6.o.2, Latest Headlines [Live Bookmarks feed to BBC ] quit loading. Any suggestions? Thanks, Bridgid.

الحل المُختار

All Replies (6)

more options

الحل المُختار

Try to create a new Latest Headlines bookmark by visiting this website:

more options

Thanks cor-el, your solution worked. Bridgid.

more options

First link gives '404 - not found'.

more options
more options

We accidentally broke this, but it should be fixed shortly. You should not need to take any action... it will recover on its own within a day or so.

For the record, this is entirely unrelated to any Firefox update. We broke how we were handling certain feed location URLs on fxfeeds.mozilla.com... it would have affected even non-Firefox users, if any are/were using this feed.

If you want to fix it yourself, you can edit the feed location to one that works. Right-click "Latest Headlines" and hit Properties. The Feed Location should be of the form:

http://fxfeeds.mozilla.com/en-US/firefox/headlines.xml

(replace your locale... en-GB, es-ES, and so on)

There is a bugzilla bug on this as well, with a technical discussion of what happened: https://bugzilla.mozilla.org/show_bug.cgi?id=692035.