can't save any article

Adams · 2026-01-11 17:42:31

Hello,
On the new published production 4.9 can’t save any article. with error

“Error: Article not saved. adam modified the article while you were editing it. If you’re sure, press the ‘Save’ button once more.”
no any other error!

No one atactlly logged in, I’m the only developer and jus have one computer and one session open. I closed the browser and opened again, no luck.

also the date shows 1968/09/25

PHP version: 8.4.15
Server time zone: America/Chicago
Server local time: 2026-01-11 11:41:07
Automatically adjust Daylight Saving Time setting?: 0
Time zone (GMT offset in seconds): America/Chicago (-21600)
MySQL: 11.8.3-MariaDB-log (MariaDB Server)

Any idea ? as explained before

Thank you

Adams · 2026-01-11 19:08:07

Please ignore, looks same issue we talked about the date issue, 4.9 published version, not compatime with MySQL: 11.8.3, for now, I just going to stick with previous version 4.9 dev version
Textpattern version: 4.9.0-dev 7-8 months old.

Thank you

Bloke · 2026-01-11 19:16:03

Adams wrote #342165:

4.9 published version, not compatime with MySQL: 11.8.3,

If we can find or develop a test environment with this version or later, we can see what the fallout is and try to fix it.

gaekwad · 2026-01-11 20:35:09

Adams wrote #342158:

also the date shows 1968/09/25

What does your hosting environment look like? Are you running locally? Are you still running Xampp? Or with a hosting organisation?

Bloke · 2026-01-11 21:53:23

The bogus date will be the reason it thinks it’s modified elsewhere. When you save, it’ll try and set the modified date to “now”, fail somehow or inject a wrong timestamp, and then next time you save, it’ll think it’s been tampered with in the meantime.

Quite why the timestamp is wrong is a mystery at present. Inspecting your Diagnostics or server environment might throw us some clues.

Adams · Yesterday 14:16:35

Hello,
I’m really getting old for development, I’m over 65 still love the development :)
anyway, I compared code 7/2025 dev with 12/2025 released, looks like a lot of changes in the date ,
in Jul 2025 files:
16 function FROM_UNIXTIME in 7 files.
in Dec 2025 files:
87 function FROM_UNIXTIME in 19 files

Those changes impacted TXP to work correctly in latest MYSQL 11

Here is example:
the article list show posted date 1964 , when I checked txp_list.php I found ‘posted’ => array( ‘column’ => ‘TIMESTAMPDIFF, Posted)’,
that cause the date to show incorrectly, while Jul 2025 file shows correctly.
I changed to ‘posted’ => array( ‘column’ => ‘UNIX_TIMESTAMP(posted)’,
showed correct date/time.

The reason for the article not saving in Dec 2025 released version is same reason.

Gentlemen, requires more work next upgrade, you will go back to fix those functions again and will get more complicated if not fixed now.

Thank you

etc · Yesterday 14:37:57

Sorry for the hassle, we will certainly fix it, though I would rather blame MariaDB for an abrupt switch. But might it be your FROM_UNIXTIME(UNIX_TIMESTAMP()) fix involved here? Basically, it replaces 1970 by the current date. Could you try FROM_UNIXTIME(1) instead?

Adams · Yesterday 14:47:02

Oh no, for me I don’t blame anyone :)
I’m sure they have a reason for all those changes, hardware, international usage and every day security , vulnerabilities makes harder to keep all together using older code. we have to move forward lol.

The FROM_UNIXTIME(UNIX_TIMESTAMP()) worked in some cases, I will try FROM_UNIXTIME(1) to see if get better result.
I will keep you posted.

Thank you all for the hard work and the valuable time .

Bloke · Yesterday 15:20:08

Yeah, to be fair we don’t officially support MariaDB, it’s just that – up till now – both MySQL and MariaDB have been broadly compatible.

We’ll try and patch 4.9.x to work with it, and I’m hoping Txp 5 will be using some form of PDO (assuming we can get our MySQL-specific queries to run cross-platform) so compatibility is then a little more organised.

etc · Today 12:51:29

I can not found any explanation why, out of a sudden, 0 becomes an invalid unix timestamp in mariadb, while 1 and even 0.001 are valid. It smells like an annoying bug. MySQL 9.4 works just fine.

Bloke · Today 13:13:08

Can we push back to MariaDB and ask if it’s an unintended regression?

etc · Today 13:18:30

Bloke wrote #342203:

Can we push back to MariaDB and ask if it’s an unintended regression?

It has a ‘wont fix’ status, which provides no explanation/workaround for me, but please take your chance :-)

Textpattern CMS

Textpattern CMS support forum

#1 2026-01-11 17:42:31