geekhack
Site Announcements and Feedback => Announcements/Feedback/Suggestions => Topic started by: demik on Fri, 12 December 2014, 22:10:07
-
EVERY SINGLE POST.
even damn PMs! it's getting annoying.
-
Ah so I guess I just double PM'ed someone.
-
Ah so I guess I just double PM'ed someone.
i just tried to reply to a PM 5 times until i just closed the tab and reopened it and it finally went through.
check my sent messages, no PMs sent.
-
Ah so I guess I just double PM'ed someone.
i just tried to reply to a PM 5 times until i just closed the tab and reopened it and it finally went through.
check my sent messages, no PMs sent.
SMF for the win!
/sarcasm
-
Had the same problem for a post. I had to write it twice because the message's body got lost after the error message. And had to close the navigator for it to work again.
-
I closed the browser and it worked fine after thay
-
just count to 12
the server sees everyone as the same user, so it just means someone is trying to post at the same time you are.
just gotta wait for imav to do something about it basically
-
I've been getting this with most of my posts it is really getting old..
-
I got it only since this week.
-
God damn this is annoying. The trick is to go into Offline mode in the browser then go back to see your post, otherwise the page returns an error and you lose the post.
Quick posting doesn't appear to have this bug.
-
If everyone is getting the same IP through the firewall or load balancer I would suggest that iMav use the "x-forward-for" header to get the real source IP through the perimeter device and then use that in the forum. Most software would support the "x-forward-for" header without modification.
-
I got it a couple of minutes ago, and I'm pretty sure I'm the only one here who would be posting on GH.
I've just got to learn to copy my post before I send it, then I can just paste it back in as the text is usually lost when I get the spurious warning message.
-
I got it a couple of minutes ago, and I'm pretty sure I'm the only one here who would be posting on GH.
I've just got to learn to copy my post before I send it, then I can just paste it back in as the text is usually lost when I get the spurious warning message.
I didn't have that reflex ... :'(
-
If I quote a post it doesn't get lost. FYI.
-
If I quote a post it doesn't get lost. FYI.
I have lost quoted posts, particularly when I was catching up on new Members Saturday night.
And I have lost quoted PMs too.
In both cases where I typed my response under the quote.
-
If I quote a post it doesn't get lost. FYI.
I have lost quoted posts, particularly when I was catching up on new Members Saturday night.
And I have lost quoted PMs too.
In both cases where I typed my response under the quote.
Huh. I kept a non-quoted post just now, so maybe it's unrelated.
I dunno when it'll be fixed, but hopefully soon.
-
Just got the error when posting a reply :(
-
This only started happening just recently. I have no idea what was changed if anything at all.
Most of the time my stuff gets saved, but it is really awful when I lose my stuff, especially when on my mobile.
-
Just lost a handful of PM's because of this lie!
-
Just lost a handful of PM's because of this lie!
(http://i.imgur.com/LhVFzmr.png)
If you're on a desktop hit this and then back, at least on Firefox it retains the text input of the previous page. Otherwise it's super frustrating.
-
This only started happening just recently. I have no idea what was changed if anything at all.
Most of the time my stuff gets saved, but it is really awful when I lose my stuff, especially when on my mobile.
Never had the problem on my phone but only on my desktop. Maybe I was lucky, I don't know.
-
God damn it! Now I have "Your last search was less than 5 seconds ago. Please try again later" ...
-
I got this when logging in this morning, "The last login from your IP was less than 2 seconds ago, please try again later"
Fix this damn 10.20.30.1 IP issue pls, ty
-
Fixed. We did some header modifications to get things logging properly, initially. However, this was out the window once we swithed to SSL. We are now logging the correct forwarded client IP.
-
Thank you iMav! :thumb:
-
Fixed. We did some header modifications to get things logging properly, initially. However, this was out the window once we swithed to SSL. We are now logging the correct forwarded client IP.
Cool. Good Job... :)
-
Fixed. We did some header modifications to get things logging properly, initially. However, this was out the window once we swithed to SSL. We are now logging the correct forwarded client IP.
Thanks!
-
So it's fixed? Nice one iMav :)
-
thanks for the fix, locking the thread now.