FieldtypeComments throws “Incorrect TIMESTAMP value” warning on save

[KarlvonKarton]

I’m using the core FieldtypeComments in ProcessWire and everything works correctly on the frontend and in the database. Comments are saved properly and displayed without issues.

However, in the admin I get a one-time SQL error after a new comment is submitted:

SQLSTATE[HY000]: General error: 1525 Incorrect TIMESTAMP value: '1777649215'

Observations:

• Difference between “error value” and stored value is consistently +3600 seconds
• No data corruption or functional issues occur

Environment:

• PHP timezone and $config->timezone both set to Europe/Brussels

The warning only appears once per comment submission and does not affect saving or rendering.

Has anyone seen this behavior before with FieldtypeComments?