New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
$7
The end is nigh.
Hello. Invoice #7283849 double my redundancy please! Thanks!
What'd you do?
Works on mobile, but not on desktop here.
working for me!
Tried updating the footer with a bit of Java to auto update the copyright date.
Redundancy doubled.
Still working on it.
Break the whole website for hours because need to update the date.
Just remove the fucking date, problem solved
Now that's a good idea!!
@raindog308
It was still working on Chrome Android when the desktop version was giving an error page.
Javascript, not Java, just to be clear.
Executive Summary: saved default.master.tpl as default.master.tpl for rollback and Smarty freaked out.
When I went in to change the master.tpl Smarty template to update the footer copyright year, I made some changes and thought oh crap, I forgot to save a "before changes" copy. Old, old sysadmin habit...
Since I was pausing and resuming vi in the shell, I undid everything back, saved it as master.tpl.prev, and then rolled forward and saved it.
Vanilla's smart cache became greatly confused by the existence of master.tpl.prev and basically threw up all over its shoelaces.
Once I saw it was broke, I assumed it was something bad in the .tpl, so naturally I copied (not moved) the .prev file into place. No luck. I grabbed the master.tpl file from last night's backup and restored it. Still no luck. At that point, everything was back exactly as it was, even the same timestamp on the file, but the desktop view was still broken.
I did a find for all files in the public_html that had changed and saw the Smarty cache compile dir had some recently-changed files. I removed the master.tpl-related files thinking Smarty was just not updating them, but it recreated them as still broken.
@FAT32 logged in and diagnosed that the existence of the .prev file was the problem. Big thanks to him!
So let this be a lesson: if you're going to make changes in production, don't try and be responsible by saving a rollback file. Throw caution to the wind or else it could come back to bite you.
Nice postmorten, I like the transparency.
You may be old or experienced, or highly professional, but we can all still make mistakes. In Russia, just under a month ago, one simple mistake caused the entire .ru domain to go down.
Backups, my friends, backups are your friend. So remember to back up all your important data regularly!
lmao.
its brave making changing on a production system!
and remember to remove cache
We like to live dangerously.
+1
Bragging. Nope you didn't, it works fine.
@raindog308
Even experienced engineers occasionally make mistakes.
The difference between lousy ones and good engineers is that the good ones can admit it - as you did.
I grinned about @FAT32. While one desperately tries a hundred ways incl. weird ones to get the mess working again, that bastard just looks at it and tells you "it's that .prev file" - and is right, haha.
Kudos to both of you!
I demand financial compensation for this outage per the SLA for my billions of dollars lost per minute!
8760 hours in a year, outage for ~2 of them? 0.000228311 * $200 = $0.0456621. We'll round it up to a nickel to show some good customer loyalty.
Let me know if you want either a Monero or Zcash wallet for my SLA compensation @FAT32
Change control approved.
It’s not displayed on mobile already, so yeah, do this
For future, Why not setup a staging site first and do your changes on it first and then release once all done or rollback?
It's a new feature, not a bug
A bit pointless, If a copyright includes a date, such as 2008, it will expire after 95 to 120 years.
I think the bigger lesson is to not make changes in production. If you're going to YOLO edit things in prod, at least use version control (Git, Mercurial, whatever) so you can roll back in case of any issues.
So, on mobile I don't even see the copyright footer part. All the trouble you guys went through was only for desktop :P