Updated to 39.5, now getting "Live bookmark feed failed to load"
Updated to 39.0 Beta 5, and now in my Latest Headlines toolbar bookmark I get "Live bookmark feed failed to load". Right-clicking and clicking 'Reload Live Bookmark' does nothing. This has happened before after certain updates, and seems only to be put right after other, subsequent updates.
Additional System Details
- Facebook Video Calling by Skype
- The Flip4Mac WMV Plugin allows you to view Windows Media content using QuickTime.
- InstantAction.com Mac Plugin
- Displays Java applet content, or a placeholder if Java is not installed.
- The QuickTime Plugin allows you to view a wide variety of multimedia content in web pages. For more information, visit the QuickTime Web site.
- Shockwave Flash 17.0 r0
- Unity Web Player version 4.3.5f1. (c) 2013 Unity Technologies ApS. All rights reserved.
- User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:39.0) Gecko/20100101 Firefox/39.0
hi, could you try to replicate this behaviour when you launch firefox in safe mode once? (this is just for testing purposes and not a general solution)
The problem does not occur when FF is launched in safe mode. I've just updated my extensions, restarted FF, and the problem remains. I should add, my 'Latest Headlines' bookmark was working fine with these same extensions prior to updating to 39.0 Beta 5.
Modified by Meatballs
could you try narrowing it down to the extension which is interfering here, by disabling them one-by-one/in batches depending on how many you have? afterwards it would probably be helpful to inform the addon developer about this...
Right, having repeated the process several times, I can say that it's the HTTPS Everywhere extension causing the problem.
ok thanks, so this probably isn't a general conflict with live bookmarks and https everywhere but only with this particular rss feed which gets "upgraded" to https but doesn't work for some reason. can you create an exception for that one page in the https-everywhere settings?
I'm reading up on that at the homepage but it's not so easy, it seems to involve writing an XML file....
I suppose for the moment we can consider this issue settled- the problem has been isolated, though not fixed- and I'll report back if I come up with a solution.
Thank you so much for your time Phillipp, you've been most helpful.