Hi, Newbie here - but running a phpBB site since 2004. Time to move on. I’ve had some success in converting my database in my Discourse test environment, but I’ve got several warnings like this: WARN – : Bad date/time value “0000:00:00 00:00:00”: mon out of range It’s been suggested that I replace occurrences like that in the phpbb_backup.sql file with 1970-01-01 for these dates before import, but they don’t occur anywhere in the file. How do I find out exactly what the script is complaining about (and what topic or post), and how do I fix it? adTHANKSvance, Dan P.S. did these records import despite the warning, or were they rejected?

Thanks, Jay. Still, I wonder why the script flagged them; and I wonder what that means for the post. Here’s a snippet from the import log, with warnings: 18112 / 24451 ( 74.1%) [292 items/min]Do you happen to know, for this example, if 18112 is the phpBB post_id? If so, you are quite right - the post got converted, and appears to have the correct dates, for both the original poster and the one who replied.

[image] shortmort37: Do you happen to know, for this example, if 18112 is the phpBB post_id? it is not. You can see the post ids in post.custom_fields['import_id']. But that’s just a counter of how many posts (or topics?) have been converted. [image] shortmort37: I wonder why the script flagged them I’m pretty sure that the post has zero or null in some date field. it’s a warning, not an error, so it did import something. If it had failed to import it, you’d get an error, I’m fairly certain. If you really care, you can modify the script to print the phpBB ID when it gets such an error, then you can track down which phpBB posts are generating these errors and look at those records to see what’s happening. [image] shortmort37: It’s been suggested that I replace occurrences like that in the phpbb_backup.sql file with 1970-01-01 for these dates before import, That date is zero in utime, so it wouldn’t change anything. I’ve never thought it was worth my clients’ money to answer this question before. If it is something you’d like to spend money on, please email me. Perhaps someone else has a better answer.

[image] pfaffman: If you really care, you can modify the script to print the phpBB ID when it gets such an error, then you can track down which phpBB posts are generating these errors and look at those records to see what’s happening. This is worth pursuing, methinks. [image] pfaffman: I’ve never thought it was worth my clients’ money to answer this question before. If it is something you’d like to spend money on, please email me. Um…thank you for your offer. It’s just that I’ve got enough of these warnings in nearly 25K posts that I’d rather be certain, than fairly certain. [image] pfaffman: Perhaps someone else has a better answer. Perhaps.

Date/time warnings in phpBB3 conversion to Discourse

Product Support Migration

pfaffman (Jay Pfaffman) January 14, 2026, 2:56pm 2

They got imported, I’m fairly certain. I just ignore these.

Topic		Replies	Views
MyBB import doesn't process on quoted posts PID and date Bug	8	3824	September 22, 2015
phpBB3 import script improvements Migration phpbb	11	2957	July 19, 2017
My phpBB Migration Journey (postgresql) Migration phpbb	23	2376	March 30, 2023
Enhancement request to phpBB3 import script Migration phpbb	39	1237	January 19, 2026
Alter topic creation date Development	4	734	November 21, 2020

Date/time warnings in phpBB3 conversion to Discourse

Related topics