Cannot reproduce IPS importer doesn't import archived thread posts

[K a M a L]

Affected version

1.5.1

When IPB forum has archiving enabled .. posts of archived threads are moved from forums_posts to forums_archive_posts and xenforo importer doesn't try to import them
This represents the majority of posts if forum is old or too big .. in my last import where archiving is enabled I lost 370k posts out of 450k so this is a major issue in my opinion

 

[puterfixer]

Bringing this topic back from the dead, as I have just completed a migration from IPB 4.something to XF 2.2.12 using this importer script.

IPB had around 700k posts from the past 17 years. For DB performance, it was set to automatically archive the posts from threads which were not active for more than 3 years. In effect, this would move the posts from the active posts table to a separate archive table, and make the threads read-only.

The XF importer imported all threads, but since it couldn't find the posts in the active posts table, it set the post ID to 0 and did not import the posts from the archive table. I could see all threads from the past 17 years, but any thread older than 3 years would return an error when opened.

As a result, I did:

• first migration, which moved all content to XF except archived posts;
• discovered the issue, forced IPB to move all archived posts back to the active posts table (normally does this with a cron entry moving 250 posts every 5 minutes, I changed that to run 50 times faster - 2500 posts every 1 minute; thankfully my web host didn't kick me out for straining their infrastructure for a couple hours);
• ran the import again and chose just the posts to be imported, but the importer re-imported all users, all forum nodes and all threads all over again, which after running for 3 hours resulted in duplicates of everything;
• deleted everything in the XF DB and started all over with the installation and import, which ran for another 5 hours.

I'm sure all of this can be avoided fairly easy by 1) also importing the posts in the archive table, 2) reusing the import log table to link already imported IDs in case an incremental import is executed, and 3) if the script is not modified, at least write a note that IPB users need to first disable the archiving feature and wait for a few hours/days for the background job to move all archived posts, before putting the forum in maintenance mode and doing the migration.

 

[XF Bug Bot]

Automated triage: Cannot reproduce

Importing posts from IPS's archive table was added as a separate 'Archived posts' import step in XFI 1.5.3. Please upgrade the importer and run that step during your import.

This is an automated assessment. A member of staff may review and update it.

 

[puterfixer]

Bro... really?

There is no version history published for the Importers, and there are no announcements for new releases since 1.5.1. So I did some searches.

Sep 2021: XF releases Importers 1.5.1

Dec 2021: OP raises issue on Importers 1.5.1

Jan 2023: I encountered the same issue with whichever was the latest importer version at the time (don't remember, didn't check, don't have it saved, might have been 1.5.2)

Mid-Jul 2024: I can find only a forum reference about someone having importers 1.5.3 - this is the version that should have corrected the bug

End-Jul 2024: XF releases Importers 1.6.1, which is the current version 2+ years later

Oct 2026: bot considers this "cannot reproduce" which is a very dismissive response implying an incorrect report at the time it was submitted, instead of "already resolved in previous version" (and therefore cannot be reproduced on current version almost 4 years later).

Agreed, bug report is obsolete and can be closed as the root cause has already been corrected in 2 subsequent releases since the versions that had the bug. But 5 years to respond with the incorrect classification? Bad bot.

 

[Chris D]

I mean, the classification is entirely correct.

The bot could not reproduce the issue. The issue was fixed in 1.5.3.

There is no implication in the bot's response that's dismissive or that the report itself was wrong. It's just factually stating that it isn't currently a reproducible issue, which it isn't, and it was fixed in the stated version, which it was.

Automated triage: Cannot reproduce

Importing posts from IPS's archive table was added as a separate 'Archived posts' import step in XFI 1.5.3. Please upgrade the importer and run that step during your import.

This is an automated assessment. A member of staff may review and update it.

Good bot