Bottlehead Forum

General Category => General Discussion => Topic started by: VoltSecond on March 28, 2014, 01:43:47 PM

Title: No unread topics found since your last visit. . .
Post by: VoltSecond on March 28, 2014, 01:43:47 PM

My computer does not like the new forum.  Every time I log in I get a "No unread topics found since your last visit" message.  I haven't changed anything since the forum changed.  I was hoping it would fix it self, but it didn't.

I use Firefox for my browser.

Title: Re: No unread topics found since your last visit. . .
Post by: Kris on March 28, 2014, 02:54:41 PM

In your browser: clear history, cookies, cache, passwords, update browser if needed and restart your firefox.

Title: Re: No unread topics found since your last visit. . .
Post by: Doc B. on March 28, 2014, 03:09:31 PM

yes, something may still be pointing to the old IP address.

Title: Re: No unread topics found since your last visit. . .
Post by: Chris65 on March 28, 2014, 05:00:20 PM

Also delete any bookmarks/favourites & log-in again and click 'Mark all messages read'.
That worked for me after someone suggested it.

Title: Seems to be fixed
Post by: VoltSecond on March 28, 2014, 06:01:13 PM

I did nothing different except to post a new thread to the general forum and it is working.   Someone in Redmond must have my name on a dart board. . .

Thanks for the help.

Title: Re: No unread topics found since your last visit. . .
Post by: 2wo on March 29, 2014, 05:30:51 AM

I found that if I log out, it works. I am guessing the new forum or maybe Firefox keeps me logged in forever, hence no new post...John

Title: Re: No unread topics found since your last visit. . .Back to being broken
Post by: VoltSecond on April 29, 2014, 08:14:17 PM

Argh.

Title: Re: No unread topics found since your last visit. . .
Post by: Grainger49 on April 30, 2014, 04:35:19 AM

I had this problem for a day or two.  I logged in and out and that didn't make a difference.  But the next time I came back I got new responses.

I'm sure my problem was caused on my end.  It must have had something to do with a Firefox update.