search

petea / sage

A feed reader for Firefox.
http://sagerss.com
27 stars 8 forks source link

Check Feeds button does not work #81

Closed petea closed 11 years ago

petea commented 11 years ago

Original author: eaka...@gmail.com (July 31, 2012 19:20:05)

What steps will reproduce the problem?

  1. Click Check Feeds Button 2.Nothing happens 3.

What is the expected output? What do you see instead?

Should see Sage checking each feed individually. See no change instead

What version of Sage are you using?

1.4.12

What version of Firefox are you using? On what operating system?

14.0.1 Windows 7

Please provide any additional information below.

I can get the feeds to check by closing and reopening Sage, but it won't check a second time.

Original issue: http://code.google.com/p/sage/issues/detail?id=82

brunomueller commented 11 years ago

Hi using Firefox 22 Sage 1.5 on windows7 I am having the same problem the "Check Feeds" button does not work. also if a feed prompts for userid and password this does not happen. Everything worked fine with Firefox21 and the previous Sage

petea commented 11 years ago

Can you tell me if you're seeing any errors in the Error Console when you click the Check Feeds button?

Tools > Web Developer > Error Console

petea commented 11 years ago

drgnwing0: do any of the errors that you're seeing mention Sage? Note that you can filter the Error Console.

On Thu, Jun 27, 2013 at 7:30 AM, drgnwing0 notifications@github.com wrote:

Same problem here. I get the following errors when I click the Check Feeds button:

Error: TypeError: this._wloPluginObj.SetFocus is not a function Source File: chrome://websitelogon/content/websiteLogon.js Line: 57

Error: TypeError: this._wloPluginObj.SetFocus is not a function Source File: chrome://websitelogon/content/websiteLogon.js Line: 64

This doesn't include the long list of errors I get beforehand that might be from the automatic feed checker (unable to tell when it checks).

— Reply to this email directly or view it on GitHubhttps://github.com/petea/sage/issues/81#issuecomment-20123424 .

drgnwing0 commented 11 years ago

Nvm, I think my problem stemmed from the fact that one of my feed links would fail to load and it leave sage in limbo "checking" that feed. Sage would stop responding after that.

These are the errors that cause it to stop functioning: Timestamp: 6/27/2013 9:43:41 AM Error: feedItem.link is null Source File: jar:file:///C:/Users/xxxx/AppData/Roaming/Mozilla/Firefox/Profiles/epx6p6au.default/extensions/%7Ba6ca9b3b-5e52-4f47-85d8-cca35bb57596%7D.xpi!/components/sageMozillaFeedParser.js Line: 116

Timestamp: 6/27/2013 9:43:41 AM Error: NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS: '[JavaScript Error: "feedItem.link is null" {file: "jar:file:///C:/Users/xxxx/AppData/Roaming/Mozilla/Firefox/Profiles/epx6p6au.default/extensions/%7Ba6ca9b3b-5e52-4f47-85d8-cca35bb57596%7D.xpi!/components/sageMozillaFeedParser.js" line: 116}]' when calling method: [nsIFeedResultListener::handleResult] Source File: resource://gre/components/FeedProcessor.js Line: 1266

petea commented 11 years ago

drgnwing0: ah, yes, that's helpful. As I suspected, this issue is probably related to #102