etc

@petecooper could you set the production status of next-demo to `Debugging`, please? More eyes less bugs...

That was me setting status to debug, but it seems to switch to testing on rebuild. Weird, this internal error. It only happens on next-demo, so must be another 8.2...

@petecooper thanks, not for the moment for me.

Something is [planned](https://github.com/textpattern/textpattern/tree/integrity) in this sense, for JS too. But for flat links this requires some server configuration, since PHP is totally bypassed. Needs investigation.

It looks like most (all?) dates are stored in db as UTC timestamps, which is great. But we have two timezones interfering: the server default one (if set) and txp...

Yes, but users date input is expected to respect `timezone_key` zone (they don't even have an idea of what the server tz is). Why wouldn't we just set the default...

I have actually tried it, and it worked fine on my localhost, but some articles `year/month/date` URL were not recognized on the demo server.

Oh, I didn't mean altering `php.ini`, just calling `date_default_timezone_set()`, which seems to act per session, like `setlocale()` etc (it would be too bad otherwise). Well, there is no real problem...

Okay, let's try it. I had no issues on localhost, but Pete's server has 2h db/server tz offset, so some articles published near midnight go west. Investigating. This actually happens...

Yes, db is UTC, but not php: ``` Server local time: 2021-08-06 00:01:00 ... Time zone (GMT offset in seconds): Europe/Amsterdam (3600) ... Database server time: 2021-08-05 22:01:00 ``` This...