This task should list all breaking changes that were introduced in MediaUploader that may present themselves when upgrading from UploadWizard. Each item should have a link to the relevant task/patch and a suggested solution. This will be later used in documentation.
**Note: the breaks should not be too //serious//. They should be mostly rare/edge cases or stuff that probably only Wikimedia uses. In short: you shouldn't have to worry about it.**
* Scripts for upgrading from older versions of UploadWizard are not shipped with MediaUploader.
** **Task/patch:** {T274913}
** **Suggested solution:** First upgrade UploadWizard to the latest (or a reasonably recent) version, then upgrade to MediaUploader.
* There is no Wikibase support. Campaign definitions that contain `statements` or `wikibase` elements will fail to validate.
** **Task/patch:** T274910 – [[https://gerrit.wikimedia.org/r/c/mediawiki/extensions/MediaUploader/+/665370 | patch]]
** **Suggested solution:** There are no plans for Wikibase support, as this was specific to Commons. Any problematic elements in campaign configs should be removed.
* There is no special patent and weapon handling for STL files.
** **Task/patch:** T274910 – [[https://gerrit.wikimedia.org/r/c/mediawiki/extensions/MediaUploader/+/665416/ | patch]]
** **Suggested solution:** This should not be a problem for non-Commons users, but if it is, please mention it in T275248. A hook interface for that could be created.
* Object references are not supported. Campaign definitions that contain `labelPickImage`, `noticeExistingImage` or `noticeUpdateDelay` elements will fail to validate.
** **Task/patch:** T274910 – [[https://gerrit.wikimedia.org/r/c/mediawiki/extensions/MediaUploader/+/665469 | patch]]
** **Suggested solution:** This was a Commons-specific feature, but if you did use it, check if your use case is covered by improved field configurability (T275264). If it's not, file a task explaining your use case, a more general solution may be added.
//Side note: it seems there will be many incompatible campaign config changes. We could consider creating an entirely new schema altogether and provide a migration script that would convert the old campaign configs to the new format.//
**Template:**
* (the issue)
** **Task/patch:**
** **Suggested solution:**