As the title say.
This would be a new migration from https://lhmn.fandom.com/vi
Check for dump files integrity before interact with them.
- XML dump from Fandom
-
JSON dump for ManageWiki (may not needed) - Images dump manually grabbed by me
PiscesKazeMGR | |
Dec 28 2022, 13:08 |
F1981531: vilhmn_pages_full.xml.7z | |
Dec 29 2022, 18:33 |
F1979947: lhmnwiki_managewiki_backup_03529819625d0743f581.json | |
Dec 28 2022, 15:11 |
F1979948: vilhmn_pages_current.xml.7z | |
Dec 28 2022, 15:11 |
As the title say.
This would be a new migration from https://lhmn.fandom.com/vi
Check for dump files integrity before interact with them.
I got the xml and may needed, ManageWiki dump.
But as long as I can't grab image files from the Fandom version, this task cannot be continued.
After like, near a day, I finally can run the dump images commands and got my self the image dump.
Just an FYI, for licensing reasons the XML must be the dump with full revisions, not only current revisions as your current one is.
Whole thing.
But as the Wiki just enabled SMW recently, I suggest you run maintenance scripts to make sure it operates properly, if it was necessary.
Wiki recreated from scratch. Please use Special:RequestImportDump to request the importing of the Fandom XML.
Hold up. Some issues here:
MediaWiki internal error. Original exception: [2592773a03123a2775cc8f45] 2023-01-19 16:15:10: Fatal exception of type "MediaWiki\Storage\NameTableAccessException" Exception caught inside exception handler. Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information
Oh and not to mention: I already put my images dump in somewhere these comments are...
MediaWiki\Storage\NameTableStore::getName falling back to primary select from content_models with id 1
The reset is not actually clean, as there are still some old settings and customized MediaWiki pages too...
And when I click for random articles, welp, it yet found one of the old post that I might certain that it was not cleaned properly...
It has been fixed by @Universal_Omega
Everything has been reset, there is almost no chance that something has not been "cleaned" properly. It would likely be from the XML that you requested to be imported.