mark page as read and refresh not working
Starting 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.
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.
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.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I have this problem also. Version: 2.x.117 (build 4901)
-
Inappropriate?Hmm. very sorry about that. This is probably a regression but we have a very hard time reproducing it and without being able to reproduce it, we are shoot in the dark. Do you see any error messages in the firefox error console right after you click on the link?
-
Inappropriate?Only a couple of warnings about the use of CharCode property.
I should have mentioned in my response (and I don't whether this is also the case for emellaich) that the link is only dead for me on category pages. On the digest page the three bottom links are still clickable and work fine. -
Inappropriate?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.
-
Inappropriate?Thanks for the clarification. I am now able to reproduce it. Will try to see if we can push a patch out tomorrow. Will keep you posted.
-
Inappropriate?Update: We have fixed this issue. This fix will be included into patch 2.x.118 (which we could be able to push out later this evening). Thanks for your help in resolving this issue.
The company says
this solves the problem
-
Inappropriate?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.
I’m frustrated
-
Inappropriate?It's now fixed for me (version: 2.x.120 (build 4906)). I only got the version with the fix in recently. Perhaps the fix wasn't pushed out as quickly as Edwin had anticipated.
What version are you using? -
Phil you are right: 2.x.118 did not go out as I expected. This fix was only included in 2.x.120. -
Inappropriate?What do I do to force an update? I tried uninstalling it and reinstalling it.
However, i think I was originally on a beta release (or I was at some time or another), and I think after the reinstallation I am now in the mainline release? Anyway, I'm now at 2.8.117 (build 4902)
Thx,
MLH -
Inappropriate?The 2.8 version you have is the "stable" less-frequently updated version of feedly. So it might not get the fix for some time. The version with the fix is at feedly.com (the 2.x version). Go there and reinstall to get the fix immediately.
You were probably on the 2.x version at first, but switched to the 2.8 version just before the fix rolled out to 2.x.
Loading Profile...




EMPLOYEE