Loading Profile...
Success! (at finding a bug in the new version)
I start on the cover page and it looks fine. To try things out I click on the first button (cover) and get a blank page. The following warnings:
-------------------------------
[feedly][bridge][received]{"rotId":"rot1","method":"loadCoverPage","arguments":[]}
[feedly][feedly][error] failed to ask page to service because NS_ERROR_NOT_AVAILABLE -- Component is not available [@745]
[feedly][analytics]cover
[feedly][reader]synchronization complete.
------------------------------
After that I can't get anything on the "what's new" page either (except an error message)
[error] failed to layout summary area because NS_ERROR_NOT_AVAILABLE -- Component is not available [@745]
And in the console
----------------------------
[feedly][bridge][received]{"rotId":"rot1","method":"loadMyPage","arguments":[]}
[feedly][analytics]my
---------------------------
In "all" and the category pages I can see everything except the article summaries (menus, title, feed titles and feed menus, empty "recommended by" section, sources) and there is space left for the article info, but no article titles or summaries.
Clicking on any of the feeds gives something like the following error:
Internal Information:
-1 -- [error] failed to askEntries.onCompleteHandler for feed/http://planetweb20.com/index.rdf , , user/12998188367222434665/state/com.google/read , 16 because NS_ERROR_NOT_AVAILABLE -- Component is not available [@745]
And in the console:
------------------------------------------------------
[feedly][bridge][received]{"rotId":"rot55","method":"goToFeed","arguments":["feed/http://planetweb20.com/index.rdf"]}
[feedly]Javascript exception during askEntries:NS_ERROR_NOT_AVAILABLE - Component is not available. Hint:feed/http://planetweb20.com/index.rdf , user/12998188367222434665/state/com.google/read , 16
[feedly][analytics]subscription/feed/http://planetweb20.com/index.rdf
------------------------------------------------------
This all seems related. I'll post again if I have more.
-------------------------------
[feedly][bridge][received]{"rotId":"rot1","method":"loadCoverPage","arguments":[]}
[feedly][feedly][error] failed to ask page to service because NS_ERROR_NOT_AVAILABLE -- Component is not available [@745]
[feedly][analytics]cover
[feedly][reader]synchronization complete.
------------------------------
After that I can't get anything on the "what's new" page either (except an error message)
[error] failed to layout summary area because NS_ERROR_NOT_AVAILABLE -- Component is not available [@745]
And in the console
----------------------------
[feedly][bridge][received]{"rotId":"rot1","method":"loadMyPage","arguments":[]}
[feedly][analytics]my
---------------------------
In "all" and the category pages I can see everything except the article summaries (menus, title, feed titles and feed menus, empty "recommended by" section, sources) and there is space left for the article info, but no article titles or summaries.
Clicking on any of the feeds gives something like the following error:
Internal Information:
-1 -- [error] failed to askEntries.onCompleteHandler for feed/http://planetweb20.com/index.rdf , , user/12998188367222434665/state/com.google/read , 16 because NS_ERROR_NOT_AVAILABLE -- Component is not available [@745]
And in the console:
------------------------------------------------------
[feedly][bridge][received]{"rotId":"rot55","method":"goToFeed","arguments":["feed/http://planetweb20.com/index.rdf"]}
[feedly]Javascript exception during askEntries:NS_ERROR_NOT_AVAILABLE - Component is not available. Hint:feed/http://planetweb20.com/index.rdf , user/12998188367222434665/state/com.google/read , 16
[feedly][analytics]subscription/feed/http://planetweb20.com/index.rdf
------------------------------------------------------
This all seems related. I'll post again if I have more.
3
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.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?That was quick!
-
Inappropriate?question: is your cover page in a category or subscription mode?
-
Inappropriate?Category.
From the start-up cover page I can read articles and open category pages and read articles within them. But at some point something goes wrong and I get the errors again. -
Inappropriate?Ok. we are going to try to reproduce it and see what might be causing [error] failed to ask page to service because NS_ERROR_NOT_AVAILABLE -- Component is not available [@745].
Please let us know if you think you have a reproducible case. -
Inappropriate?I get the blank page whenever I click on the cover icon. After that everything (except possibly "the wall") is messed up as described above.
-
Inappropriate?ok..so let me make sure I understand:
1. you start the browser.
2. click on the feedly orange button (what is your default start page URI?)
3. click on the cover (and instead of seeing the content of the cover you see a blank page? -
Inappropriate?Yes. After (2) the start-up a normal page appears (typically cover for me).
Without doing anything else, I click on the cover icon on the menu bar and the good page is replaced with a nearly blank page (it had the main menu bar, wallpaper, and top line menu items.
-
Inappropriate?Phil,
Hmm. So you start the browser, get the cover loaded and then click on the cover icon? Sorry for being slow but I do not understand "the start-up a normal page appears (typically cover for me)."
Could you please cut and past the URL you see in the browser nav bar after step 1 and after step 2 please?
Thanks,
Edwin -
Inappropriate?Sorry to not be clear. Leaving aside my sloppiness, I don't have a language down pat for describing my path and observations.
Yes to your first question. (There was no point other than experimentation in clicking on the cover page icon as I was already on the cover page. However I later changed my start-up page to "my", started back up and got the same effect described after clicking on the cover icon.) I should have said "at feedly start-up a normal cover page appears."
URL 1: http://cm.my.yahoo.com/
URL 2: http://www.feedly.com/feedly#cover (in a separate tab) -
Inappropriate?Thank for the clarification Phil. We are going to try to reproduces and track it down. Will let you know as soon as we have more information.
Question: how many categories do you have defined? -
Inappropriate?Currently five. The fifth one is usually empty as I only recently added it and have only put in three or so feeds.
I'm closing down for tonight, so I'll check back tomorrow. -
Inappropriate?I have the same issue. I started my browser this morning and saw that feedly now loads from http://www.feedly.com/feedly#cover and not from chrome://.
On starting the browser I got an error message that
chrome://feedly/....../app.htm does not exist. I do not remember the exact file though.
Now that feedly loads from feedly.com I get errors like :
"Internal Information: -1 -- [error] failed to askEntries.onCompleteHandler for feed/http://ajaxian.com/atom.xml , , user/17443005707757300069/state/com.google/read , 16 because NS_ERROR_NOT_AVAILABLE -- Component is not available [@745]"
When I click on a category, from what I see in firebug, a single POST request is made and the response contains the items for the first feed in the category. No errors appear but nothing else is retrieved and no items are displayed no none of the feeds in the category.
Hope that helps.
By the way http://s3.feeddo.com/production/boot/... returns "Not Found".1 Comment
Add a comment
This solves the problem
-
A bit more info. Actually only the "Picture and summary" View does not work. And the Magazine View as well. All other views work fine. -
Inappropriate?Hi Ivan.
Thanks for the boot image missing heads up. That has been fixed.
Regarding the "Component is not available [@745]" error, a couple other people have been reporting it but we are not able to reproduce it.
Can I ask you a favor: Can you please point your browser to http://update.feeddo.com/release/feed... and re-install and re-start your browser (we put a few more debug messages in that build).
After the restart that you please go to:
1) http://www.feedly.com/feedly#my and see if that page loads
2) clear the firefox error console and go to http://www.feedly.com/feedly#cover and see if that loads and if it does not, please email me a screenshot of the messages sections of the firefox error console to edwink@devhd.com?
Thank you very much! -
Inappropriate?Just sent you the screenshot. By the way, is it my imagination or did feedly run from chrome:// yesterday?
-
Inappropriate?Thanks Ivan. Got the screenshot, it will help reduce the perimeter.
Regarding chrome:// to http://. It was not your imagination. See http://edwink.devhd.com/2008/07/18/st... for more information.
I will keep you posted as soon as we have a better understanding of what might be causing the problem.
-Edwin
I’m thankful
-
Inappropriate?Ivan, Phil:
When you get the chance, could you please install:
http://update.feeddo.com/release/feed... and re-install
After the restart that you please go to:
1) http://www.feedly.com/feedly#my and see if that page loads
2) clear the firefox error console and go to http://www.feedly.com/feedly#cover and please email me a screenshot of the messages sections of the firefox error console to edwink@devhd.com?
This should allow use to better understand what is causing the "Component is not available" issue.
Thanks for your patience.
Edwin -
Inappropriate?Just sent you the screenshots.
It may or may not be important but when I view a category in Magazine view or "Title and Pictures" View I get "Component is not available", but in Titles view everything works fine. The same holds for individual feeds. -
Inappropriate?Ivan. I just replied to your email with yet another build to try out.
Regarding the view, do you get the error with every feed or a specific feed?
Which OS are you running Firefox on?
Thanks,
Edwin -
Inappropriate?Every single feed shows this error when in "Picture and Summary" mode.
I run Debian with firefox nightly build. The same happens with the normal Firefox.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.2pre) Gecko/2008071704 Firefox/3.0.2pre -
Inappropriate?hmm. The exception is being thrown in DOMNode.setAttribute...I am wondering if firefox has different ways of materializing the DOM in different OS. Would you happen to have a window or mac machine would could access your feedly from? This would help us determine why we are not able to reproduce the problem you are seeing (see if it is because OS or because we have a different set of feeds).
-
Inappropriate?Ok Ivan. I have one last test for you if you have the time please:
http://update.feeddo.com/daily/feedly...
We changed a couple of things. It is a blind shot because it is not clear what the initial root cause was but it might be enough to avoid the exception. Please let us know if you have the chance to try it.
Thanks,
Edwin -
Inappropriate?Just FYI, I installed it on windows and everything works fine. The only error in the console is:
Failed to load XPCOM component: C:\Documents and Settings\Administrator\Application Data\Mozilla\Firefox\Profiles\6kib3wmy.default\extensions\feedly@devhd\components\nsIFeedlyBoot.idl -
Inappropriate?Thanks for all you help ivan. We pushed a new build which includes the latest changes we put in based on our email exchange. That should address the problem regarding the initial rendering.
Tomorrow, we will look into the next set of issues you reported. If you get the chance, you can move back from the debug build to the mainline:
http://update.feeddo.com/release/feed...
Thanks again for all the time you spent this evening trying to help you troubleshoot this problem: next time you are in the San Francisco Bay Area, the dinner and the drinks are on us.
Edwin -
Inappropriate?With the version of feedly that asked to be installed this morning (version: 1.0b4.5 (build 1747)), I am no longer able to immediately reproduce this problem by clicking on the cover icon.
I am able to get the errors again through a longer process that I had noticed last night. If I go to the dashboard and read several feeds, after reading articles in 3-4 feeds I get:
--------------------
-1 -- [error] failed to askEntries.onCompleteHandler for feed/http://www.commentarymagazine.com/blogs/index.php/feed/ , , user/12998188367222434665/state/com.google/read , 16 because NS_ERROR_NOT_AVAILABLE -- Component is not available [@743]
---------------------
In the console, I have:
--------------------------------------
[feedly][bridge][received]{"rotId":"rot15","method":"hide","arguments":[]}
[feedly][feedly][onHashChanged] loadPage( uri:dashboard)
[feedly][bridge][received]{"rotId":"rot1","method":"loadSubscriptionPage","arguments":["feed/http://www.daybydaycartoon.com/atom.xml",0,false]}
[feedly][error] failed to askEntries.onCompleteHandler for feed/http://www.daybydaycartoon.com/atom.xml , , user/12998188367222434665/state/com.google/read , 16 because NS_ERROR_NOT_AVAILABLE -- Component is not available [@743]
----------------------------------------
And from then on I get the same error on every feed I try to read and I get the errors on the various front pages.
I'll try loading the debug version you mentioned above and do the sequence you requested above. -
Inappropriate?Ok, I did as you requested. I don't reproduce the error anymore with the cover icon in this debug version either, but here is the output of the error console after clicking on cover as requested:
---------------------------------------------
[feedly]>>>> [cover page] list length:4
[feedly]>>>> [cover page][0][object XPCNativeWrapper [object HTMLDivElement]]
[feedly]>>>> [cover page][0] set home done
[feedly]>>>> [cover page][0] set page done
[feedly]>>>> [cover page][0] set list label done
[feedly]>>>> [cover page][0] set list URI done
[feedly]>>>> [cover page][0] set recommendations done
[feedly]>>>> [cover page][0] set part done
[feedly]>>>> [cover page][0] set display done
--------------------------------------------------
The part after the list length repeats 3 times (one for each category I suppose). I doubt this is helpful given that the error isn't reproduced. I'll try poking around in this debug version to see if I can't reproduce the error some other way. -
Inappropriate?Here you go (this is debug version @@@ (build #@#) if that means anything). Poked around from the dashboard as described above and eventually got the error:
-------------------------------
Internal Information:
-1 -- [error] failed to askEntries.onCompleteHandler for feed/http://www.patentlyo.com/patent/atom.xml , , user/12998188367222434665/state/com.google/read , 16 because NS_ERROR_NOT_AVAILABLE -- Component is not available [@23]
-------------------------------
There error console has:
--------------------------------
[feedly][bridge][received]{"rotId":"rot1","method":"loadSubscriptionPage","arguments":["feed/http://feeds.feedburner.com/Econbrowser",0,false]}
[feedly][bridge][received]{"rotId":"rot45","method":"selectEntry","arguments":["4798730427320392523"]}
[feedly][feedly][onHashChanged] loadPage( uri:dashboard)
[feedly][bridge][received]{"rotId":"rot1","method":"loadSubscriptionPage","arguments":["feed/http://www.patentlyo.com/patent/atom.xml",0,false]}
[feedly][error] failed to askEntries.onCompleteHandler for feed/http://www.patentlyo.com/patent/atom.xml , , user/12998188367222434665/state/com.google/read , 16 because NS_ERROR_NOT_AVAILABLE -- Component is not available [@23]
--------------------------------
When I try to go to the cover page afterwards I get:
----------------------------------
[error] failed to render cover page because NS_ERROR_NOT_AVAILABLE -- Component is not available [@23] -- hint: columns 4 -- rows: 4 -- list: 4
----------------------------------
And on the console:
---------------------------------
[feedly][cover page] [error] failed to render cover page because NS_ERROR_NOT_AVAILABLE -- Component is not available [@23] -- hint: columns 4 -- rows: 4 -- list: 4
--------------------------------- -
Inappropriate?OK Phil. Thanks for the additional information. We have 10 additional people running into this problem so it is going to be our top priority today. We will keep you posted. -Edwin
-
Inappropriate?Phil. We just pushed out 1.0b4.6. Fixed on problem and improved error reporting in bunch of other places. Next that you get a feedly break, could you please restart the browser so that if you run in this problem again we can (hopefully) get a little bit more information?
Thanks,
Edwin -
Inappropriate?Looks good so far. Definitely having a hard time reproducing the error now. I'll keep you posted if it crops up again.
-
Inappropriate?Unfortunately, I still expect it to be there so please keep an eye out!
-
Inappropriate?I'm definitely getting the same error. I mostly occurs at tag or individual feed level. Occasionally, I get issues with Cover or What's New.
I'm running 1.0b4, and can't seem to find 1.0b6 anywhere in the links you've posted.
I’m frustrated
-
Inappropriate?Stephen,
Can you please point your browser to http://update.feeddo.com/release/feed... re-install and restart your browser. If you get any errors, please let us know what specific error messages you are seeing and if there is additional information in the firefox error console.
Sorry for the inconvenience,
Edwin -
Inappropriate?I just got an email from Phil about things seeming to be back to normal. I am going to close that bug so that if someone sees a problem, they can create something new and we can track it down again. Thanks everyone for the help addressing this issue and sorry for the turbulence.
EMPLOYEE
