Firefox Extension not Working
No matter what site I go to, the Firefox PostRank extension does not detect feeds. Thanks in advanced!
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Did the extension prompt you to authenticate with your PostRank account when you first installed it? If everything worked ok you should have seen a popup which would have taken you to the postrank.com login screen.
-
No it didn't. I'll uninstall and reinstall it now.
Edit: Still nothing. I guess we're getting to the root of this problem. I'm using FF 1.0.10 on Mac OS 10.4.11. -
I'm sorry. I meant Firefox 3.0.10. -
Inappropriate?Try the following steps:
1. In your locations bar, type in: "about:config"
2. In the selector field: type in "aiderss", you should see several keys popup
Are the *.oauth.token or *.oauth.secret keys set to anything? -
No, neither of them are. -
Hmmm, so it's not getting through the initialization phase. From the same window, can you double click on "aiderss.debug" key (it should turn to 'true'). Once that's done, reboot your browser and hit 'ctrl-shift-j', do you see any aiderss/postrank related errors in that window? -
Here's one that may be relevant:
Error: postrank is not defined
Source File: javascript:%20postrank
Line: 1 -
The "No feed" grey box is exactly what I've been getting since I first installed the extension. -
Hmm, very strange. You're not seeing any other mentions of postrank in the debug output? If not, I really don't know what's going on. -
Unfortunately no. Just repetitions of the message I mentioned earlier. -
Inappropriate?Ok. I've solved part of the problem. When I disabled half of my Firefox extensions (to troubleshoot another product, Evernote's web client), the authentication window came up.
Up to this point, I've been accessing the site via my Google account and am still able to do so. But when I try to do so in the authentication window I am asked for a password. I have not created one on the site so I'm left with leaving it empty or using my Google password; neither of which work.
Here are some errors mentioning postrank that have been appearing in the error console since I've gained access to the authentication window, many of which repeat numerous times:
Warning: Unknown property 'text-overflow'. Declaration dropped.
Source File: http://www.postrank.com/stylesheets/g...
Line: 526
Warning: Expected declaration but found '*'. Skipped to next declaration.
Source File: http://www.postrank.com/login
Line: 1
Warning: Error in parsing value for property 'font'. Declaration dropped.
Source File: http://www.postrank.com/login
Line: 1
Error: chrome://postrank/content/authenticate.js:45 ::: chrome://postrank/content/authenticate.js:45 ::: authorizeToken request failed : : {
}
Source File: chrome://postrank/content/authenticate.js
Line: 45
Source Code:
chrome://postrank/content/authenticate.js
Error: chrome://postrank/content/authenticate.js:15 ::: chrome://postrank/content/authenticate.js:15 ::: getRequestToken success: : {
[created_at]: "2009-05-13T21:52:52Z"
[updated_at]: "2009-05-13T21:52:52Z"
[token]: "pKB9OxbXtKFiOI7tR4Cw"
[authorized_at]: "null"
[id]: "19987"
[user_id]: "null"
[secret]: "Vy0QpgodXom9g1eurzGEIcLipTKTlSi6ImzxKEWn1U"
[invalidated_at]: "null"
[client_application_id]: "4"
}
Source File: chrome://postrank/content/authenticate.js
Line: 15
Source Code:
chrome://postrank/content/authenticate.js
Warning: Error in parsing value for property 'white-space'. Declaration dropped.
Source File: http://www.postrank.com/stylesheets/g...
Line: 576
Warning: Unknown property 'word-wrap'. Declaration dropped.
Source File: http://www.postrank.com/stylesheets/g...
Line: 576
Warning: Unknown property 'border-radius'. Declaration dropped.
Source File: http://www.postrank.com/stylesheets/l...
Line: 39
Warning: Error in parsing value for property 'margin-bottom'. Declaration dropped.
Source File: http://www.postrank.com/stylesheets/l...
Line: 220
Error: chrome://postrank/content/postrankStatusOverlay.js:345 ::: chrome://postrank/content/postrankStatusOverlay.js:345 ::: findFeedId: http://getsatisfaction.com/aiderss/to..., reqUrl http://getsatisfaction.com/aiderss/to... cache: undefined
Source File: chrome://postrank/content/postrankStatusOverlay.js
Line: 345
Source Code:
chrome://postrank/content/postrankStatusOverlay.js
Error: chrome://postrank/content/postrankStatusOverlay.js:373 ::: chrome://postrank/content/postrankStatusOverlay.js:373 ::: checking feedCache :: http://getsatisfaction.com/aiderss/to... :: undefined
Source File: chrome://postrank/content/postrankStatusOverlay.js
Line: 373
Source Code:
chrome://postrank/content/postrankStatusOverlay.js
Error: chrome://postrank/content/postrankStatusOverlay.js:345 ::: chrome://postrank/content/postrankStatusOverlay.js:345 ::: findFeedId: http://weblogs.newsday.com/sports/spe..., reqUrl http://weblogs.newsday.com/sports/spe... cache: [object Object]
Source File: chrome://postrank/content/postrankStatusOverlay.js
Line: 345
Source Code:
chrome://postrank/content/postrankStatusOverlay.js
Error: chrome://postrank/content/postrankStatusOverlay.js:373 ::: chrome://postrank/content/postrankStatusOverlay.js:373 ::: checking feedCache :: http://weblogs.newsday.com/sports/spe... :: [object Object]
Source File: chrome://postrank/content/postrankStatusOverlay.js
Line: 373
Source Code:
chrome://postrank/content/postrankStatusOverlay.js
Error: chrome://postrank/content/postrankStatusOverlay.js:374 ::: chrome://postrank/content/postrankStatusOverlay.js:374 ::: checking uriCache :: http://weblogs.newsday.com/sports/spe... :: undefined
Source File: chrome://postrank/content/postrankStatusOverlay.js
Line: 374
Source Code:
chrome://postrank/content/postrankStatusOverlay.js
I’m confident
-
I think the Fasterfox extension was preventing the authentication window from appearing. -
Aha, thank you for tracking that down! We'll investigate the Fasterfox conflict. -
No problem! Any idea about what may be preventing me from accessing my Google account in the authentication window? Like I said before, I have no problem using it on the site when it's in a Firefox tab. -
Inappropriate?So, when you click the "Google" button in the authentication window, what do you see? I get a Google sign in page, which asks for my Google email and password (what I would use to sign into GMail, for example).
After entering that, I get a dialog asking if I want to sign into Postrank.com with my Google account.
After clicking "Sign in", I am able to authorize the extension. Is any of that process working for you?
-
The Google sign-in actually uses OpenID behind the scenes, so that's not incorrect. You should have had to provide an email and agree to the TOS the first time you logged in with Google on our site. Did that not happen? -
Inappropriate?I can't recall whether or not that was the case. Regardless, I do know that I never provided a password to the site, which seems to be implied by the following screen, which appears in the authentication window after I provide my e-mail address and agree to the Terms of Service and Privacy Policy.
I’m puzzled
-
Very strange...
The behaviour you're describing is what should happen when you log in with a new OpenID which we haven't seen before. Are you logged into a different Google account, by chance? -
No. I'm logged into the same Google account that I intend to sign into the AideRSS extension as.
Loading Profile...




EMPLOYEE
EMPLOYEE

