Loading Profile...
TypeError -- g is null
I've got this error in the digest
[error] failed to layout top area because TypeError -- g is null [...js/10101_fx-core_4524.js@377]
If i reinstall feedly - the latest one - and then restart firefox it works fine just for the first time I open the digest, then the error shows up again.
"cover" and "latest articles" are still working fine. if I switch to any category I get a
Sorry. You just ran into a bug!
[feedly version:]
[navigator user agent:]
error (even if in a category with a + in the category name it shows the "TypeError -- g is null" error
thanks
[error] failed to layout top area because TypeError -- g is null [...js/10101_fx-core_4524.js@377]
If i reinstall feedly - the latest one - and then restart firefox it works fine just for the first time I open the digest, then the error shows up again.
"cover" and "latest articles" are still working fine. if I switch to any category I get a
Sorry. You just ran into a bug!
[feedly version:]
[navigator user agent:]
error (even if in a category with a + in the category name it shows the "TypeError -- g is null" error
thanks
I’m thankful
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.
The company marked this problem solved.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Thanks for the heads up. Will try to investigate today and keep you posted.
-
Inappropriate?I've checked again the category related error. There are 3 kind of category names:
- only [a-z] chars -> sometimes typeerror
- [a-z] mixed with a + (plus) -> sometimes typeerror
- [a-z] mixed with a - (minus) -> always the bug error
moreover, from error console when clicking on the "cover" link:
[feedly][fn][callback][trapping][error] failed to callback because TypeError -- g is null [...js/10101_fx-core_4524.js@377]
I’m confident
-
Inappropriate?Update. We were able to trace this message thanks to the error message. It was related to a bug which corrupted the feedly cache. This bug has been fixed in the 2.x.095 patch we pushed out and everything should be back to normal next time you restart firefox. Thanks for your help!
-
Inappropriate?Update. We were able to trace this message thanks to the error message. It was related to a bug which corrupted the feedly cache. This bug has been fixed in the 2.x.095 patch we pushed out and everything should be back to normal next time you restart firefox. Thanks for your help!
-
EMPLOYEE
