-
-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rebuildData.php / ContentHandler.php: No handler for model 'xml' registered in $wgContentHandlers #1448
Comments
I'm guessing MW 1.24?
No.
This is the issue, which means some settings on your wiki doesn't correspond to the expected As we parse the whole page we also need to parse anything else (including other parser functions) as it may influence the state of property values which is why we cannot skip them. https://www.mediawiki.org/wiki/Manual:$wgContentHandlers
Since this isn't related to SMW you can skip this with
For this we need a specific example and it would best to have this reproducible on http://sandbox.semantic-mediawiki.org/wiki. Are you using the VisualEditor? [0] https://phabricator.wikimedia.org/T47750 |
Still using MW 1.24.2 here. --ignore-exceptions did not work at first (the exception did interrupt the XML was used on some pages, which may have been the issue, so I cleaned up VisualEditor is not installed (and never has been). 2016-03-11 10:28 GMT+01:00 mwjames notifications@github.com:
|
I just simulated a similar error by setting
yet, if I use
So,
https://www.semantic-mediawiki.org/wiki/Help:RebuildData.php#Important_Notes |
Thanks, then the docs must be outdated and incomplete because https://www.semantic-mediawiki.org/wiki/Help:Installation/Upgrade_from_SMW_1.9%2B_for_MW_1.22%2B 2016-03-11 14:12 GMT+01:00 mwjames notifications@github.com:
|
Can we close this? |
We're done here I think. 2016-03-13 22:57 GMT+01:00 mwjames notifications@github.com:
|
Update: The new, upgraded site running SMW 2.4alpha is now online at vanhamel.nl/codecs. Transferring the site to a local computer has been a wise choice, all the more because it allowed me to do things I could not have done without shell access. Running rebuildData.php seems to have had positive effects on the database: it has now gone down dramatically in size from about 1.8 to 1.1 GB, although a small part of this is attributable to other factors. Unfortunately, two specific IDs* were causing a bottleneck: because of --ignore-exceptions, rebuildData.php was not interrupted but instead it continually attempted to process these same IDs over and over again, resulting in quite a drain on my computer's resources, to put it mildly. About 24GB became unusable to the point where I had to shut down my computer. The log shows numerous repetitions of the same report pointing to an issue with XML - similar to the one reported earlier. The source of the problem is beyond me and I haven't exactly solved this other than telling rebuildData.php to skip the problematic IDs, which then allowed rebuildData.php to complete the data refresh. This may be an issue of long standing since I can remember how earlier attempts at doing a "Data repair and upgrade" from Special:SMWAdmin appeared to 'hang' indefinitely. (*P.S. These IDs could not be discovered in the Object ID lookup from Special:SMWAdmin) |
If you know the ID then have a look at the
That should not happen and a way to replicate this behaviour would be much appreciated.
Adding a range (-s/-e option) before and after the ID that causes the issue together with option -v should output a more verbose info about the object in question.
If the entity is known try to the delete the related page (using MW standard |
Following the fatal error mentioned in #1446, I tested the pre-release 2.4 version of Semantic MediaWiki. Hitting refreshData.php now gave me a different error:
Perhaps this is related to #295?
Another odd thing I noticed is the appearance of the words 'off' and 'on' surrounding a link when that link is produced by a query. The link comes from a value of a property that has the datatype 'Text'.
The text was updated successfully, but these errors were encountered: