Coming from here: https://octobercms.com/support/article/rn-4

This question comes to mind, do all tables made with ...

    $table->timestamps();

... needs to be updated with the solution stated in the article?

And also, do I have to re-write the old migration scripts to make all custom timestamp columns nullable? Like:

    $table->timestamp('col_name')->nullable();

Note: using the new method from the article

    DbDongle::convertTimestamps('users', ['created_at', 'updated_at', 'last_login']);

... renders the plugin useless for older October instances. This is a huge drawback imho. How do other authors deal with this?

Moved this topic to: https://octobercms.com/forum/post/build-332-invalid-timestamps-with-mysql-strict-mode-2

Answered here: http://stackoverflow.com/questions/38348102/how-to-implement-dbdongleconverttimestamps-as-workaround-of-invalid-timestamps