|
|
Post by Tim on Apr 2, 2017 20:05:32 GMT -6
Good news is V17 is officially here!
Official Site: gos.talij.com
There was a hiccup this morning where the site got reset AGAIN. Not sure how that happened yet (wasn't me), but I've taken steps to hopefully prevent any unexpected resets in the future.
IF YOU MADE AN ACCOUNT PRIOR TO RECEIVING THIS EMAIL, YOU MAY NEED TO RECREATE YOUR CHARACTERS!!
Since we were within the first 12 hours of the site, I'm just going to role with it. The reset was a little after 9AM CDT (3PM GMT), so any character created within 20 hours of that will have the right amount of turns.
I humbly apologize for this happening (again!) and I will do my best to make sure issues like this stop happening!
Go Team!
|
|
|
|
Post by Tim on Apr 3, 2017 0:59:51 GMT -6
Ok. It happened again and this time I have NO IDEA how it could have happened. It did happen on a page load by me though, so I do believe I am somehow triggering it. So here's what needs to happen.
V17 is currently postponed until I can figure this out. I will NOT let the age go on with a ticking time bomb of a potential reset. I will dig into this ASAP to track down the issue, and as soon I do we will reschedule an official launch again.
Feel free to play around on the V17 version of the site for now as I work. There WILL be another reset though, so don't get too attached.
I am super sorry. I'm stumped as to how this is happening, but I WILL figure it out and we WILL move on. I'll keep you all posted in on the forum and hopefully resolve this quickly.
Again. Sorry.
|
|
|
|
Post by kaldar on Apr 3, 2017 6:21:22 GMT -6
You are backing up the database now .... just in case , right ?
|
|
|
|
Post by Tim on Apr 3, 2017 7:10:54 GMT -6
I back it up periodically, but the my hosts doesn't allow automatic backups so I manually backed it up about once a week last age after the reset then.
|
|
|
|
Post by kaldar on Apr 3, 2017 11:07:51 GMT -6
Ger knows more about web programming than me. He suggested it was probably a case of the script being cached in memory. Alternatively, maybe you thought you recompiled the code to new code but didn't. Something like that.
My suggestion is to :
Clear your cache, remove the code that resets the age, try to run the script that resets the age (that now shouldn't work), if that is good to go then you are clear.
Then for now you will need to put the code back in to reset the age. Reset the age, then repeat the same steps. After you verify that you can't run the reset script even when actively trying to do so, then you are good for now.
Long term fix is to remove this script from the browser level and run it from the database level that cannot be run accidentally, only manually.
Go Team ?
|
|
|
|
Post by Tim on Apr 3, 2017 13:24:29 GMT -6
Thanks. Those are all good suggestions. The caching issues is the part I'm still not clear on how it was triggered, but I suspect you guys are probably right.
My plan is basically what you laid out here. The additional step I plan on taking is removing the permissions to create and drop DB tables from the account that is used to make all the DB updates after a reset is done so even if I missed something and it gets triggered it the reset won't happen. Made some minor tweaks to the reset scripts to not insert things that initialized by the reset scripts if they already exist so they don't get duplicated.
Long term is indeed to pull the reset stuff out of the web interface. Will make those tweaks for next age.
So now that I have a plan (which I plan to have fully implemented tonight), the question is when do we do the official launch. Not a fan of doing the launch mid-week, but we'll see. I'll figure it out tonight and will send out a FINAL email (not trying to spam everyone). Will be Wednesday night at the earliest, as I want to give at least some notice to everyone.
|
|
|
|
Post by Seitaarin on Apr 3, 2017 17:28:41 GMT -6
or change reset script to not drop/delete but instead rename+recreate blank slate, so you have an archived version at all times, and then delete the archive if appropriate with a separate process
|
|
|
|
Post by Seitaarin on Apr 3, 2017 17:33:48 GMT -6
oh and if you do that, don't forget to create either an incremental in your archived table naming convention, or even better create a tracking table with the archive data, table names, times the script ran, what process called it exactly etc etc ... that way you don't overwrite previous archives with hardcoded archive table names. You probably know all that stuff anyways so this is likely wasted effort, but it's a simple thing easily overlooked, so meh  |
|
|
|
Post by Tim on Apr 3, 2017 19:49:14 GMT -6
I've made some changes and taken some precautions, so I have a some confidence that the site reset situation has been handled sufficiently. So that means we need to plan a new date for launch. Normally I like to do launches on weekends, but under the circumstances, I don't want to keep you guys waiting any longer than I have to. On the other hand, I want to make sure everyone has enough notice to make plans accordingly. So...
V17 will relaunch on this Thursday night (4/6) at 9PM CDT (3AM GMT on 4/7).
I'll take every precaution I can to make sure things are stable this time. Thank you all for your patience with me and hope to see you all Thursday night!
|
|
|
|
Post by kaldar on Apr 6, 2017 6:35:18 GMT -6
Please ...
1) Change the graphic display on the front end to reflect that a new age is starting and today is the start day.
2) If there is any way you can grab the email list from the forum and send an email with an actual email address source it might be a good idea as all of your emails are still going to junk. The reason we might not be getting more players is they simply aren't being notified.
|
|
|
|
Post by Tim on Apr 6, 2017 18:43:47 GMT -6
1) Yep. I was planning on updating that tonight.
2) I can't get the email list from the forum without going through every member and grabbing it, which is painful and not maintainable. It is what it is.
|
|
