Anyone else get an error like this?

[szlamany]

I've gotten this error twice now - this time (and I believe the last time) when clicking on an e-mail notification link...

[Hack]

What browser are you using?

I don't get that, but I do get this ALL the time. The only way I can get around it is to go into IE properties, delete all cookies and then delete all off line content. This is not a problem with this site however as I do not get this error at home. So, my question would be do you get your error regardless of what computer your are on?

[szlamany]

Using IE7...

I think it's only happened on my "e-mail/forum workstation" on my desk at work.

It's only happened twice - so it's hard to say if it will happen on my laptop.

To get around it I simply close all my VB IE windows and open a fresh one - travel to the VB site...

Then if I re-click the e-mail notification link it will work properly.

I hate having to drop all my cookies and clear all content - I've got so many sites I visit...

[Hack]

Did this ever happen when you used IE6?

[si_the_geek]

This occasionally happens to me using FireFox.. usually after making a really long post, when previewing the next post I'm writing (no problem when the 'next' post is done without a preview).

Simply deleting the following two VBForums cookies solves it:
JPnyc_postCookie
bbthread_lastview

[szlamany]

It never happened with IE6...

And Si - I think it's related to having windows open with really long replies just made and such. I usually have IE open 3 or 4 times with VB forum threads in them...

[si_the_geek]

Yep, the "JPnyc_postCookie" stores the last post you made or previewed (for the "LastPost" bit above the Reply/Quick Reply box).

I'm not sure why it gets sent to the forums, as theoretically it is only needed client-side (but then I haven't inspected the code to check!).


I usually find that clearing just that cookie is enough, but sometimes need to clear bbthread_lastview too.

[szlamany]

I never use Quick Reply - what does clicking LAST POST actually retrieve into that window and why would you want to use that??

[si_the_geek]

It's on both the Quick-Reply box and the main Reply page (in both cases, just above the area you type in).

It simply replaces the current text with the last text you posted/previewed... which is useful if your browser crashes etc.

[szlamany]

Sometimes when I put a lot of effort into a reply - and knowing I've been burned by browser crashes before - I copy/paste the text into NOTEPAD just in case.

Are you saying that I don't need to do this - that LASTPOST will retrieve my last post?

[si_the_geek]

Correct.

(as a warning tho, it may be removed soon - so check that LastPost is still shown above the edit box before you rely on it!)

[JPnyc]

It's the last post cookie. If the post exceeds 4k that's the limit a cookie can hold, so you get that error. That won't happen in the new version we upgrade to next week, since the lastpost cookie will no longer be there.

[bluehairman]

Someone could have gave you a solution already, but I have one

I don't get that, but I do get this ALL the time. The only way I can get around it is to go into IE properties, delete all cookies and then delete all off line content. This is not a problem with this site however as I do not get this error at home. So, my question would be do you get your error regardless of what computer your are on?

If you get firefox you can set the properties to clear cookies, ect. when it closes. That could help what you have. Also it does it much faster (very fast) and doesn't cause firefox to "lock" up like IE6. Hope that helps.

[penagate]

Yep, the "JPnyc_postCookie" stores the last post you made or previewed (for the "LastPost" bit above the Reply/Quick Reply box).

I'm not sure why it gets sent to the forums, as theoretically it is only needed client-side (but then I haven't inspected the code to check!).


I usually find that clearing just that cookie is enough, but sometimes need to clear bbthread_lastview too.

All cookies get sent regardless of whether they are set client or server-side.