Thread:KockaAdmiralac/@comment-9605025-20191028042947/@comment-27345308-20191029003658

Andrewds1021 wrote: Thanks for the general procedure. I was thinking along similar lines. The difference for me is that I am not sure if the SHA1 tag is going to present an issue with generating the page content pre-import. I was also thinking of keeping all the revisions so they show when viewing the history of the page. These two things combined, I was thinking of using the pre-import script to just merge the page histories and then make the composite page via the wiki. Hmm, that might work but it does require more HTTP requests that the script should make. If you want to keep all revisions, you could repeat the process of generating page content for only the main thread, then for the main thread and first reply, then main thread and second reply... and add all those as fabricated revision nodes into the XML tree. As for the SHA1 tag, I think I never had issue with those when I manually edited exported XML, but if you think you will you could just generate the SHA1 hash of the revision content for each revision.

Andrewds1021 wrote: I have never used AjaxThreadDelete myself but I do get some results when using "list=deletedrevs". So I guess someone else must have at some point. If you do not have a habit of deleting thread pages the MediaWiki way instead of using Fandom's thread quasi-deletion functionalities I would suggest not caring about deleted threads. Those are most likely just going to be thread replies left by spambots whose contributions were cross-wiki cleaned up by the VSTF or vandals locally nuked with WHAM or its alternatives and probably are not worth restoring. If you want to keep threads and replies that were removed/deleted using Forum's regular "Remove"/"Delete" buttons, you don't need to check deleted revisions - these are already listed when you check the list of all pages.

Andrewds1021 wrote: Yeah, I forget which endpoint is was (maybe "list=logevents") but it seemed clear that deleted pages are given "pageid=0". I guess this means they just get a new ID when they get restored? That would be consistent with the issue of restoring threads. Either way, I am curious if restored threads can be viewed using the new page ID. From experimenting around, I know that the code behind the Thread namespace just checks to see if the number matches the page ID of a page in an acceptable namespace. For instance: Thread:1753547. I have been fighting the urge to see what happens when you reply to a reply. Restored threads were given a new ID after restoration, yeah. They can be viewed using the new page ID, but their replies will be gone and they will not appear on any board.

Replying to any page is possible. If it's a main namespace page, it'll count as an article comment. If it's a comment, it'll count as a reply to that comment. If it's a reply to a comment, it'll count as a reply to that reply... except that it won't actually display as a reply to a reply because comments support only one level of replying. You can also comment on absurd namespaces, such as MediaWiki. Unsurprisingly, this works even with Article Comments disabled.

If it's a Message Wall, it won't work unless you specify the title in. When you do, the title gets removed anyways, and the thread doesn't appear on the wall. I'm not sure if the user gets a notification, either. When you reply to a thread reply I don't think it actually shows up except for in your contributions. When looking through recent changes, nobody can tell what you replied to and where on Earth has your reply gone. I don't know what else can you do, but if you want to play with it here's the code you can run in your console to reply to a page with any ID:

Andrewds1021 wrote: Okay, so there is one small setback. Apparently if you are searching multiple pages you can only retrieve the latest revision. A bit of a pain but I guess I could just look through all the revision parentids and whichever ones aren't "0" I place the page title in a list with others and then go through the list one at a time. This is also easier if you have the export of all thread revisions in an XML tree.