Loading Profile...
Please give Flock users a chance
Feedly was working (not very nicely) on Firefox 2 and Flock 1.2 and flawlessly on Flock 2beta. Since this morning I can't get it to work on Flock 2beta. Since Flock 2 is firefox3 and both flock and feedly share the same target group (social networkers) please do not be so strict on which browsers feedly can work on and re-enable flock support
I’m dissapointed
2
people have 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.
The best solution from the company
-
Yannis. The fix is out. If you restart your flock, you should get upgraded to 1.0b4.3 and should be able to access feedly.
Regarding the user agent, it ends with Firefox/3. xxx Flock 2.xxx
I tested it on my local machine and it worked. Please let us know if for some reason it does not work as advertised on your machine.
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hello Yannis. Thanks for the heads up. If flock 2 is firefox 3, then we should be able to enable flock 2. Can I ask you a favor: do you know what it the user agent string for flock 2?
Thanks and sorry for the inconvenience. -
Inappropriate?Yannis: fixed. feedly should now be able to work with flock 2 beta (and any other version of flock based on firefox 3). The fix will go out either later this evening or tomorrow and will be part of 1.0b4.3
Thanks for the suggestion! -
Inappropriate?Way to go !
(...still trying to figure out what a "user agent string" looks like)
;-)
-
Inappropriate?Yannis. The fix is out. If you restart your flock, you should get upgraded to 1.0b4.3 and should be able to access feedly.
Regarding the user agent, it ends with Firefox/3. xxx Flock 2.xxx
I tested it on my local machine and it worked. Please let us know if for some reason it does not work as advertised on your machine.
The company says
this solves the problem
-
Inappropriate?By the way, thanks for asking nicely: it makes all the difference in the world! -Edwin
-
Inappropriate?@ Edwin : Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008071523 Firefox/3.0.1 Flock/2.0b2 (most probably)
Thanks a lot ! Problem partially solved, feedly loads on flock now, but many things are not working, specifically the "click to see more categories" and the "add/import more sources and social connections" buttons, the "more" link, the feed-specific buttons ("toggle subscription favorite status", "mark all as read" and "actions related to this subscription"). The right-column does not open the links, either.
Seems too complicated. But flock upgraded to beta-2 just yesterday, so it might be a browser-related problem. I'll try it on my other PC on Monday (where I still have beta-1 installed) and I'll let you know !
Thank you for all the great help ! -
Inappropriate?Hi Yannis,
I am able to reproduce the error. There seems to be some conflict in the JSON parser:
[feedly][bridge][error] failed to process message {"rotId":"rot1","method":"popupOtherCategories","arguments":[]} because TypeError -- JSON.parse is not a function [...nsion/feedlyExtension.js@34]
It is late tonight. Will try to take a look tomorrow and see if this is a simple name space collision or something more serious.
Thanks again for the heads up. -
Inappropriate?Re-opening this bug so that we can look at the JSON parser issue tomorrow.
-
Inappropriate?Ok. It was a simple name collision around JSON parser. fixed. You should get the fix next time you restart the browser. 1.0b4.5
-
Inappropriate?It works !!! It's a beauty ! :) Good night and have a nice weekend !
I’m jumping around !
-
Inappropriate?I am having a similar problem with flock 2.0b2. When I load feedly I get the following error
[error] failed to layout summary area because NS_ERROR_NOT_AVAILABLE -- Component is not available [@743]
-
Inappropriate?Got a follow up message from kim saying that this problem was resolved in 1.0b4.7. Closing this thread so that if anyone is experiencing a similar problem with 1.0b4.7 or higher they can notify us and we can track it down.
EMPLOYEE
