Testing whether re-logging re-synchs my account with the forum engine

[JasonPratt]

As many of you know, the forum engine has been acting weird this weekend, desynching us from sending p-mails, sometimes telling us our post time has expired, sometimes posting us as though it's late April 2012.

Migrating the forum to a new site didn't fix this problem, though it was a good try.

I'm currently experimenting with whether having logged out and logging my account back in manually (rather than by cookie) re-synchs my account with the forum server.

So far, so far, although it's more of a negative deduction test: if it fails, then I know it didn't work.


Edited to add: this post worked, sent 11/11/18, 9:53pm my time. (I mention this on my test post by editing after posting, to see if the system is retroactively redating member posts backward. I haven't caught it doing so yet, but I saw some minor evidence that way earlier today.

[Jarhead0331]

The migration has nothing to do with the problem. We needed to do the migration regardless of the tech issue and our hosting service advised that it’s best to complete the migration and then address the technical issue we are experiencing.

As of last night, the migration was still not complete anyway. Not sure why it’s taking so long.

I really think the issue is server side. I wouldn’t waste too much of your time trying to sort it on your end. We are working on it and we’re sorry for any inconveniences it’s causing in the meantime.

Thanks.

[Destraex]

It's not just me!!!

[Pete Dero]

This morning (night in the US) everything was back to normal.

Now the date has jumped back to 30 April 2012....

Did someone recently drive a Dolorean ?

[Destraex]

I reckon the server has the y2k bug

[JasonPratt]

Back at the office this morning, I logged out manually and re-logged in, with my Surface Pro 3 (Win 8.1).

While I haven't had any of my prior desynch problems, I have noticed that the forum sometimes thinks I need to log in again (despite the forever cookie). This was not happening last night at home (also Win 8.1 machine, but a much moxier Falcon Northwest) after my manual logout/login. No before now on either machine.

Since there's a difference after the experiment, I thought I should report it, in case this helps any theories. 

[Jarhead0331]

Back at the office this morning, I logged out manually and re-logged in, with my Surface Pro 3 (Win 8.1).

While I haven't had any of my prior desynch problems, I have noticed that the forum sometimes thinks I need to log in again (despite the forever cookie). This was not happening last night at home (also Win 8.1 machine, but a much moxier Falcon Northwest) after my manual logout/login. No before now on either machine.

Since there's a difference after the experiment, I thought I should report it, in case this helps any theories. 

Really appreciate it. I hope its an easy fix. My fingers are crossed that the migration will solve it in and of itself without having to do any other troubleshooting.

Famous last words.

[Gusington]

Jason you want a job here? It wouldn’t pay much but you could be like our Egon.

[Jarhead0331]

Jason you want a job here? It wouldn’t pay much but you could be like our Egon.

...and the fringe benefits are great. All the hookers and blow you can eat.

[Huw the Poo]

Have you updated the forum software recently Jarhead?  If so it's possible there was a regression.

[JasonPratt]

I am terrified beyond the capacity for rational thought at the offer.

 


(Actually, I have some years of experience being an admin and moderator for a BBCode forum. Much to my annoyance we had to change to a different engine earlier this year, and I'm still not used to it. At all.)

Edited to add: manual login / re-log test continues with no problems other than the forum occasionally wanting me to relog in again (but not this time).

[JasonPratt]

Blankedy blank blanken!!! 

I forgot to edit a timestamp verification after my post for this morning (where I logged out and logged back in manually).

I can't absolutely confirm that the system retroactively punted the post date back to 2012. But that has happened to me twice today -- thus at least decisively confirming that manually logging out and in again doesn't solve the problem on users re-synching (or doesn't solve it permanently) -- and I at least didn't notice a bad original dating when I posted those "2012" posts earlier today.

Edited to add: Nov 12, 2018, 1:48:30pm Central Standard, correctly timed for this post.

[Huw the Poo]

Nice Ghostbusters reference!

[Gusington]

 

Offer still stands.

I've had some odd things happen in the last 12 hours but only for 1-2 seconds at a time and only on a PC desktop.

All is smooth on a my iPhone and iPad.

[JasonPratt]

Gus,

your prior post now reads stamped at April 30, 2012, 4:17:43 am (my local time). I don't know if I noticed that when I saw it earlier this afternoon.

New data change: all the front page link feeds are gone. Can't say if I've noticed any of the extra advertising code this evening while checking around, either.

Edited to add: this post got datestamped properly, Nov 12, 2018, 5:14pm-ish local time.