A user is converting a phpBB3 forum to Discourse and encountering warnings about invalid date/time values (0000:00:00 00:00:00) during import. shortmort37 is concerned about the cause and impact of these warnings, asking how to identify the problematic posts and whether they were imported. pfaffman reassures that the posts were imported despite the warnings, explaining that the issue stems from zero or null date fields in the database. They clarify that the counter in the import log (e.g., 18112) does not correspond to the phpBB post ID, which can be found in post.custom_fields['import_id']. pfaffman suggests modifying the import script to log the phpBB IDs for debugging but notes that resolving this is not typically worth the effort unless the user is willing to pay for it. shortmort37 expresses a desire to investigate further due to the high volume of warnings.
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.
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.
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.
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.