Last modified: 2009-08-04 09:41:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 13598 - Spezial:Pages with Semantic Errors
Spezial:Pages with Semantic Errors
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Markus Krötzsch
Depends on:
  Show dependency treegraph
Reported: 2008-04-02 21:17 UTC by DaSch
Modified: 2009-08-04 09:41 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description DaSch 2008-04-02 21:17:13 UTC
For maintaince it would be very helpful if there would be a spezialpage listing all pages that have an semantic error.
Comment 1 Thomas Bleher 2008-04-03 08:54:36 UTC
FWIW: I posted a patch a while ago that added all such pages to a special category:
Comment 2 Siebrand Mazeland 2008-08-11 11:05:29 UTC
Re-assign to extension developer for triage/comments.
Comment 3 Markus Krötzsch 2009-08-04 09:41:49 UTC
As of SMW 1.4.3, there is a special property "Has improper value for" that records input errors. A special page is not needed, since an #ask query or the Property page of that property can be used to show all pages with errors. The property relates the page where an error occurred to the property that was used for the problematic annotation. This also allows SMW to automatically repair errors when the datatype of a property is changed (if the error was caused by having the wrong type in the first place).

Note You need to log in before you can comment on or make changes to this bug.