Recent activity
Subscribe to this feed
emellaich replied on November 05, 2009 03:32 to the problem "mark page as read and refresh not working" in Feedly:
emellaich replied on November 04, 2009 14:31 to the problem "mark page as read and refresh not working" in Feedly:
Sorry, but no go for me. I never received an update. So Instead I uninstalled feedly and reintalled it. Still no joy. I can't mark a page as read.
This is becoming quite a problem because of my fumble fingers combined with a (IMHO) poor interface design on your part.
Since I can't mark a page as read, I have to mark each article as read. This means that I click the X box at the end of each headline. Unfortunately, as I attempt to clear a bunch of headlines I start clicking X boxes and eventually click one next to a news feed. In this case, this doesn't just hide the feed, it deletes the feed from feedly, and I have no way of knowing what I just deleted or knowing how to get it back (there is no undo that I know of).
So, I still have no mark read / refresh / back to top links and I also have a new complaint about the ability to unsubscribe too easily by clicking on the X boxes.
I am sorry, but this is really making it difficult to do my daily tasks. And, unfortunately, Feedly is too important to me :) or :( . If you are not able get to this I'll need to start another search for a feed reader.
emellaich replied on November 04, 2009 13:52 to the problem "smtp settings are correct. Why can't I send email with AT&T?" in Mozilla Messaging:
So, two things that occur to me.
1) Are you sure your new password is correct? What about caps/caps-lock? This is the type of mistake that I often make :(. Try to reset your password again. I think their web interface for this is: http://att.yahoo.com/mail
2) You don't mention the version of Thunderbird you are using. One problem I had in going to 3.x was that it wanted to automatically check "Use Secure Authentication". Even though I have a secure connection I don't have secure authentication. Try changing that setting (if you have 3.x) it is in the SMTP settings.
MLH
emellaich replied on November 03, 2009 02:37 to the problem "mark page as read and refresh not working" in Feedly:
I am similar to Phil, in that it is a problem with category pages, but not with the digest.
I am running feedly version: 2.x.117 (build 4901) on FF 3.5.4
Edwk, you ask about error messages in the FF console right after I click the link. What link are you talking about?
I can't actually click the 'mark page as read' link because it is not a link. All I see is gray text that is non-clickable -- it's just normal text, not a link. Or are you talking about something else?
I tried looking at page source to see what you were actually outputting on the two pages -- but of course it was just the javascript call.
I tried installing firebug, but I admit I don't really know how to use it. I saw the text that was on the pages (from firebug) but I still couldn't see the actual HTML to know what the difference was between the working and non-workingpages.
I am expecting to see a mis-matched quote mark somewhere, but I don't know how to look at the raw HTML on my screen.
emellaich reported a problem in Feedly on November 02, 2009 16:25:
mark page as read and refresh not workingStarting this weekend, the links in the bottom right corner:
back to top • mark page as read • refresh
do not work -- they are no longer links
I have this problem on two different computers running FF (whatever the latest production release is). On is Win 7 and one is Vista.
emellaich asked a question in Feedly on October 29, 2009 17:47:
Alltop rssalltop rss is not working
I use the alltop android rss at android.alltop.com
When you click on an article headline you get sent to a "bad redirect" page on google.
emellaich shared an idea in Feedly on September 22, 2009 23:43:
A comment on the problem "SMTP Server Issues. Apple Mail works. Postbox receives, but doesn't send." in Postbox, Inc.:
On my system, the Gmail SMTP connection should be set to "STARTTLS", but the authentication should be unchecked. The trick is unchecking the authentication because when you first migrate or set up a new connection the wizard seems to want to check it and that will leave it not-working. – emellaich, on September 21, 2009 00:49
emellaich replied on June 15, 2009 15:04 to the problem "SMTP Server Issues. Apple Mail works. Postbox receives, but doesn't send." in Postbox, Inc.:
I'm not sure if this is a related problem, but here is what I can report.
1) Sending was fine with Thunderbird 2.x
2) I had this problem with Thunderbird 3.xbeta and Postbox
3) I had migrated the settings over from Thunderbird 2.x
4) I was receiving the following message:
Sending of message failed.
An error occurred sending mail: Unable to authenticate to SMTP server mail-relay.iu.edu. The server does not support any compatible secure authentication mechanism but you have chosen secure authentication. Try switching off secure authentication or contact your service provider.
After inspecting the SMTP settings, I noticed that postbox had picked up a new setting. There is now a checkbox for "Use secure authentication". My migrated settings were set up as:
Use secure authentication
SMTP over SSL
so I unchecked use secure authentication, but kept SMTP over SSL checked and everything worked fine. This suggests that you may need to investigate how the checkbox for secure authentication is populated -- since it isn't a field in the SMTP account settings for thunderbird.
emellaich replied on June 15, 2009 00:20 to the idea "apply a filter to junk mail" in Postbox, Inc.:
Thanks for your thoughts and your response. However, that doesn't really solve my problem.
I want things to happen automatically. Ideally, I would like to add my own rules to the junk filter, but using a filter would work.
Currently, when my students send messages with the class name in the subject line (e.g., K321) a rule automatically sends it to a K321 folder. However, sometimes it is snagged as junk mail instead.
Manually applying a filter as you suggest is overkill, since this particular account only has a handle full of junk messages at any given time. It is easier to eyeball them and pull them out manually. The problem is that I don't always think of checking junk mail. So, I would like a rule that is automatically applied that rescues things from junk.
I'm not sure when the best time is to run this automatic rule. Junk mail can be populated by Postbox, but it can also get populated by the mail server (gmail or exchange depending on the account). Therefore, checking when postbox sends messages to junk may not be sufficient. Probably, I would set it to check the junk folder automatically every XX minutes.
emellaich shared an idea in Postbox, Inc. on June 13, 2009 21:14:
apply a filter to junk mailI'd like to be able to apply a filter to mail in the junk mail folder. This would be let me specify certain subjects or domains that should be rescued from 'junk' automatically.
emellaich replied on June 13, 2009 21:07 to the problem "How does one send plain text?" in Postbox, Inc.:
emellaich replied on October 18, 2008 14:59 to the problem "Crash again with 1.2.57 and FF 3.1b1 with Tracemonkey enabled" in Feedly:
emellaich replied on October 18, 2008 05:01 to the problem "Crash again with 1.2.57 and FF 3.1b1 with Tracemonkey enabled" in Feedly:
emellaich reported a problem in Feedly on October 17, 2008 20:22:
Crash again with 1.2.57 and FF 3.1b1 with Tracemonkey enabledI had a problem loading the newest feeedly on FF 3.1 with tracemonkey and 1.2.57 (again).
I appreciate your paitence with this, and I understand that I am running a beta browser version.
So, the symptoms were similar to last time with one difference. The first time I loaded FF it seemed to hang. Neither the start page nor the feedly update appeared to load. Eventually, I shutdown FF and tried to reopen it. It became stuck in this cycle of opening it and going directly to a crash screen.
After several tries I went to my copy of FF 3.0.3 and opened everything just fine. Then I went to FF 3.1 again and it now worked.
As far as diagnostic info, I can report that everytime (including the first time that it looked like FF hung during the loading, but didn't crash) FF downloaded the entire feedly file (299KB). Here is what I saw from the FF crash report:
====================================================
Add-ons: {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}:0.7.5.5,abhere2@moztw.org:3.0.20081005,{097d3191-e6fa-4728-9826-b533d755359d}:0.7.6,{d95e614b-c28e-43af-a326-ca590e18abd6}:1.4,{987311C6-B504-4aa2-90BF-60CC49808D42}:2.0,{D4DD63FA-01E4-46a7-B6B1-EDAB7D6AD389}:0.9.6.3,{b9db16a4-6edc-47ec-a1f4-b86292ed211d}:3.3,feedly@devhd:1.2,foxmarks@kei.com:2.1.0.14,handytag@elitwork.com:1.0,{FDD8ECF0-451A-414D-8C8F-7B7F78B0ECD3}:1.3.3,support@lastpass.com:1.32,locationbar2@design-noir.de:1.0.3,LogMeInClient@logmein.com:1.0.0.395,{1650a312-02bc-40ee-977e-83f158701739}:26.6,{1ced4832-f06e-413f-aa14-9eb63ad40ace}:0.68.1,pencil@evolus.vn:1.0.2,refractor@developer.mozilla.org:0.2.1,{02450954-cdd9-410f-b1da-db804e18c671}:0.95,{AE93811A-5C9A-4d34-8462-F7B864FC4696}:3.26,{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}:0.5.7,{dc572301-7619-498c-a57d-39143191b318}:0.3.7.2,{d33c2f7c-b1e6-4d46-ab0e-be1f6d05c904}:1.4.9,{0fa2149e-bb2c-4ac2-a8d3-479599819475}:1.4.5,{10c62ce3-3794-4c18-a881-481733c1a425}:1.3.5,{e968fc70-8f95-4ab9-9e79-304de2a71ee1}:0.6.11,zotero@chnm.gmu.edu:1.0.7.r3393,chromifox@altmusictv.com:1.0,{972ce4c6-7e08-4474-a285-3208198ce6fd}:3.1b1
BuildID: 20081007144708
CrashTime: 1224274218
InstallTime: 1224026839
ProductName: Firefox
SecondsSinceLastCrash: 17
StartupTime: 1224274215
Theme: Chromifox
URL:
UserID: 2fb8e5ec-409b-49e0-8e0a-0386942c2c0a
Vendor: Mozilla
Version: 3.1b1
This report also contains technical information about the state of the application when it crashed.
=========================================================
emellaich replied on October 17, 2008 01:02 to the question "Serious feedly bug - crashes 3.1 beta with tracemonkey on 1.2.55" in Feedly:
ps. In regard to the size of my 'friends', I don't really follow anyone. I added 22 friends from some getting started page you had posted; however, I never really visit that tab. If it helps you guage the total size of my feedly, I've attached a screenshot of my dashboard.
However, I don't think this is the new problem. The problem I originally posted at the top of this thread occurred when I opened feedly, and therefore it might be related to the size of the thread downloaded.
This subsequent problem occurs when I open FF (not feedly) and feedly tries to upgrade itself to 1.2.55. At this time I haven't tried to open feedly, so it shouldn't have tried to download any feeds. Its just the action of FF downloading and upgrading feedly (I assume).
emellaich replied on October 17, 2008 00:53 to the question "Serious feedly bug - crashes 3.1 beta with tracemonkey on 1.2.55" in Feedly:
Mikael is correct about what you need to do in order to turn on tracemonkey. It is not automatically on in 3.1, I suspect it is alpha.
I can't replicate the problem since it came from the upgrade to 1.2.55. Once the upgrade loaded in 3.0 it was also uploaded in 3.1. In order to duplicate this problem I would need to:
1) uninstall feedly
2) install the previous version of feedly
3) open firefox 3.1 and let it try to download 1.2.55 again.
Unfortunately, I don't have time today to try this out for you. I might be able to do this during the weekend.
Michael
emellaich asked a question in Feedly on October 17, 2008 00:02:
Serious feedly bug - crashes 3.1 beta with tracemonkey on 1.2.55Me again, running ff 3.1 beta with tracemonkey.
Your patch 1.2.55 created a serious error. I can't open FF 3.1 it bombs when you try to open it and it tries to download 1.2.55. This occurs each time you attempt to open it -- its not just the first time.
I assume it was trying to load and install 1.2.55. Anyway, I was able to open FF 3.0.3. It d/l and opened the feedly update. Then when I reopened FF 3.1 feedly 1.2.55 was already installed and everything was OK. (Haven't tried feedly yet to see if it actually works.)
Michael
emellaich replied on October 16, 2008 17:03 to the problem "Feedly and FF 3.1 beta 1 with new javascript engine enabled." in Feedly:
emellaich reported a problem in Feedly on October 16, 2008 15:37:
Feedly and FF 3.1 beta 1 with new javascript engine enabled.I have been using the FF 3.1beta 1 with the new js engine (is it called tracemonkey?) The good news is that I can report much faster performance. However, Feedly has stopped working. It goes to load a page and then it crashes the entire browser and closes the browser.
I briefly see your splash page that includes a link to 'load your feedly'. Then, it doesn't hang, it just crashes and closes quickly.
| next » « previous |
Loading Profile...

