We had a little outage over at LET.

And I’m to blame.

It was all to change a single character in the site’s footer.  Previously it said “2008-2021” for copyright and I thought it was time to update it.

Vanilla Templates

LowEndTalk runs on Vanilla Forum and it uses Smarty templates.  This is a very common templating engine.  WHMCS also uses it.

If it was a .php file, I’d probably change the line to something like

2008-<?php echo date("Y"); ?>

But Smarty doesn’t run through PHP.  I had a notion to put in a little JavaScript function that would update a div tag, and I started screwing around with it.

The relevant file is themes/$THEMENAME/views/default.master.tpl.  When I went to change it, I thought “I should save a ‘before’ copy so I can back out easily”.  So I saved default.master.tpl.prev.

And then all hell broke loose.

Vanilla’s cache became greatly confused by the existence of master.tpl.prev and basically threw up all over its shoelaces.  The site started spitting out the raw template code instead of processing the template.

I immediately 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. Once it was removed, the problem vanished.

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.

No, Actually the Lessons Are…

OK, OK, don’t do things in production without testing them in a dev environment.

And turns out there is a Smarty way to solve this problem:

{$smarty.now|date_format:"%Y"}

I’ll, um, test that first before putting into prod.

• Author
• Recent Posts

raindog308

Dread Lord of LowEnd Content at LowEndBox

I'm raindog308, techno polymath and long-time LowEndTalk community Administrator. My technical interests include all things Unix, perl, python, golang, shell scripting, vintage operating systems such as MVS, and relational database systems such as Oracle, PostgreSQL, and MySQL.

I also enjoy using LEBs! I have an empire of little guys for VPNs, larger guys for apps, and big guys for databases and storage. When I'm not in front a screen I'm into German Shepherd dogs, quality knives, target shooting, theology, tabletop roleplaying games, and forest hiking.

I enjoy writing technical articles here on LowEndBox to help people get more out of their systems. You can find me on LowEndTalk @raindog308

Latest posts by raindog308 (see all)

• Happy Birthday, HostHatch!Celebrating 13 Years in Business with Awesome Deals! - April 28, 2024
• RackNerd Now Accepting Payments via USDT TRC-20, USDC-TRC20, TRX, BTC, LTC, ETH, and More Across Ethereum (ERC-20), Polygon, Solana, Tron (TRC-20) Networks - April 27, 2024
• Level Up Your Marketing and Social Media with These FREE Courses on Udemy! - April 26, 2024