So IE 11 apparently has some well known cookie problems. It is suggested to try to override the automatic cookie handling option. (this can be done by going to Internet options>privacy>advanced>override automatic cookie handling). If this doesn't work it may be an issue with current bugs in IE11.
Other notes of interest about IE11 cookies:
-cookies are turned off by default (need to be on for L19 functions lik emark forums read to work properly)
-there is a bug that loses cookie information (link to microsoft connect bug ID 810700)
-refreshing the page changes your session ID (link to microsoft connect bug ID 809923) [supposedly this bug is connected to the previous one but you never know for sure until at least one of them is actually worked out]
All Read not working
-
Gohst
- Dies in gote
- Posts: 53
- Joined: Sun Jan 23, 2011 2:03 am
- GD Posts: 800
- Location: Seattle, WA
- Has thanked: 3 times
- Been thanked: 5 times
Re: All Read not working
Yep, I have already overridden automatic cookie handling, and said "accept all" in both cases. No real difference. I still haven't gotten any time to really dig into this further.
Thanks for the pointers. However, if the bugs that you link to are as stated, it's interesting that they aren't yet fixed.
Anyway, Chrome continues to have no issues.
Thanks for the pointers. However, if the bugs that you link to are as stated, it's interesting that they aren't yet fixed.
Anyway, Chrome continues to have no issues.
-
Gohst
- Dies in gote
- Posts: 53
- Joined: Sun Jan 23, 2011 2:03 am
- GD Posts: 800
- Location: Seattle, WA
- Has thanked: 3 times
- Been thanked: 5 times
Re: All Read not working
Finally solved!
It took a while, but I finally figured out a solution to this, for IE 10 and 11 users. The bottom line is that cookies are no longer stored as individual files. Plus, all the changes that I made above (using the Internet Options dialog, and even the F12 debugging options) do NOT appear to get rid of cookies, or enable tracking cookies the way you might expect.
Anyway, the solution is found in a file called WebCacheV01.dat, which is found at C:\Users\<username>\AppData\Local\Microsoft\Windows\WebCache, where you replace <username> with your user name. This is a data base file that MSFT uses to store lots of downloaded stuff, including cookies. It is used for more then IE, which means that it is almost always in use. You won't be able to just go to that folder and delete it. If you do delete it, you lose all your cookies and saved login information, but that's what I wound up doing.
The trick to deleting (or renaming) this file is to reboot your machine and *immediately* navigate to that folder and rename/delete the file, without opening any other programs. The file will immediately be recreated by the OS, and your 19x19 "all read" problems will be solved.
You may have some programs that run at startup that open the WebCacheV01.dat file, in which case you'll have a hard time renaming/deleting it even after a reboot. If so, you may have to terminate the offending programs with Task Manager before you can get rid of the file. If all else fails, search the Internet for WebCacheV01.dat, for more ideas.
It took a while, but I finally figured out a solution to this, for IE 10 and 11 users. The bottom line is that cookies are no longer stored as individual files. Plus, all the changes that I made above (using the Internet Options dialog, and even the F12 debugging options) do NOT appear to get rid of cookies, or enable tracking cookies the way you might expect.
Anyway, the solution is found in a file called WebCacheV01.dat, which is found at C:\Users\<username>\AppData\Local\Microsoft\Windows\WebCache, where you replace <username> with your user name. This is a data base file that MSFT uses to store lots of downloaded stuff, including cookies. It is used for more then IE, which means that it is almost always in use. You won't be able to just go to that folder and delete it. If you do delete it, you lose all your cookies and saved login information, but that's what I wound up doing.
The trick to deleting (or renaming) this file is to reboot your machine and *immediately* navigate to that folder and rename/delete the file, without opening any other programs. The file will immediately be recreated by the OS, and your 19x19 "all read" problems will be solved.
You may have some programs that run at startup that open the WebCacheV01.dat file, in which case you'll have a hard time renaming/deleting it even after a reboot. If so, you may have to terminate the offending programs with Task Manager before you can get rid of the file. If all else fails, search the Internet for WebCacheV01.dat, for more ideas.
-
Gohst
- Dies in gote
- Posts: 53
- Joined: Sun Jan 23, 2011 2:03 am
- GD Posts: 800
- Location: Seattle, WA
- Has thanked: 3 times
- Been thanked: 5 times
Re: All Read not working
Well, the problem came back, in a few days. It wasn't important enough at the time to trigger a switch to Google Chrome, but I have finally switched for other reasons (IE seems to have gotten distinctly buggy and slow in the last year, enough so that it is finally worth the minor pain of switching in order to get better performance).
We'll see if that fixes the "all read" issue, but I expect that it will.
We'll see if that fixes the "all read" issue, but I expect that it will.
-
Gohst
- Dies in gote
- Posts: 53
- Joined: Sun Jan 23, 2011 2:03 am
- GD Posts: 800
- Location: Seattle, WA
- Has thanked: 3 times
- Been thanked: 5 times
Re: All Read not working
[Update] Never mind, I've found it! In any list of Posts, if you click on the little icon in front of the thread title (with the tiny arrow pointing at a document), it will take you to the first unread post in that thread. Hovering over that little icon gives you a tooltip of something like "View first unread post". So the feature *does* exist. Am I the only one who hadn't found it?
[Original Text]
So, there is still an issue, but it's not important enough for a new thread.
Now that I've finally switched to Chrome, threads are marked "read" after I open them. However, when there are new posts on one of my "read" threads, it doesn't change back to "unread" status. It seems to me that GoDiscussions.com worked differently... when new posts were made to a "read" thread, there was a way to easily go back and read *only* those new posts. That is, the "read" status remembered not only the thread, but the post within the thread, where you had previously finished reading.
Am I misremembering?
Is there a way to get similar functionality with our current software?
[Original Text]
So, there is still an issue, but it's not important enough for a new thread.
Now that I've finally switched to Chrome, threads are marked "read" after I open them. However, when there are new posts on one of my "read" threads, it doesn't change back to "unread" status. It seems to me that GoDiscussions.com worked differently... when new posts were made to a "read" thread, there was a way to easily go back and read *only* those new posts. That is, the "read" status remembered not only the thread, but the post within the thread, where you had previously finished reading.
Am I misremembering?
Is there a way to get similar functionality with our current software?
-
xed_over
- Oza
- Posts: 2264
- Joined: Mon Apr 19, 2010 11:51 am
- Has thanked: 1179 times
- Been thanked: 553 times
Re: All Read not working
Gohst wrote:[Update] Never mind, I've found it! In any list of Posts, if you click on the little icon in front of the thread title (with the tiny arrow pointing at a document), it will take you to the first unread post in that thread. Hovering over that little icon gives you a tooltip of something like "View first unread post". So the feature *does* exist. Am I the only one who hadn't found it?
Oh, cool!
I've never noticed that before.
Be warned, however, that there is a bug with the "view first unread post" functionality. Regardless of how many posts per page your settings are, if the number of new posts spills out onto the second page before you've read them all on the first page, then the "view first unread post" will take you to the first post of the second page, instead of the first unread post still on the first page.
But I wonder now, if its because I've already opened the first page, instead of using this newly found link. I'll have to test that.
- Bonobo
- Oza
- Posts: 2224
- Joined: Fri Dec 23, 2011 6:39 pm
- Rank: OGS 13k
- GD Posts: 0
- OGS: trohde
- Universal go server handle: trohde
- Location: Lüneburg Heath, North Germany
- Has thanked: 8262 times
- Been thanked: 924 times
- Contact:
Re: All Read not working
… works for me, been using it since I joined the forum.xed_over wrote:[..] the "view first unread post" functionality
Nope, not here. (I was quite tempted to edit out all the “you”s hereRegardless of how many posts per page your settings are, if the number of new posts spills out onto the second page before you've read them all on the first page, then the "view first unread post" will take you to the first post of the second page, instead of the first unread post still on the first page.
I’d bet on this.But I wonder now, if its because I've already opened the first page, instead of using this newly found link.
“The only difference between me and a madman is that I’m not mad.” — Salvador Dali
-
xed_over
- Oza
- Posts: 2264
- Joined: Mon Apr 19, 2010 11:51 am
- Has thanked: 1179 times
- Been thanked: 553 times
Re: All Read not working
Bonobo wrote:… works for me, been using it since I joined the forum.xed_over wrote:[..] the "view first unread post" functionalityNope, not here. (I was quite tempted to edit out all the “you”s hereRegardless of how many posts per page your settings are, if the number of new posts spills out onto the second page before you've read them all on the first page, then the "view first unread post" will take you to the first post of the second page, instead of the first unread post still on the first page.)
I’d bet on this.But I wonder now, if its because I've already opened the first page, instead of using this newly found link.
I'm quite sure it'll fail for you too, but its difficult to notice and test.
First, you've got to remember the last time you looked at some particular thread. Maybe there were only 8 posts on it and you've read them all the last time you looked at it.
Then the next time to look at the thread, maybe there's now 12 posts and suddenly 2 pages (at the default 10 post per page).
The "view first unread post" link should take me to post #9 (my first unread post, and still on the first page), but it doesn't. Instead, it takes me to post #11 (the first post on the next page), skipping two posts that I haven't yet read.
This only happens when the posts initially spill over onto the second page. Threads longer than 3 or more pages work as expected again.
I first noticed this when I had my settings at 40 posts per page. Less annoying on less active threads.