Page MenuHomePhabricator

MediaWiki:* vs. importTextFile.php vs. update.php
Closed, ResolvedPublic


Gentlemen, I have determined that if one uses importTextFile.php to
write MediaWiki:* items, then one must be prepared to do so again
after each run of update.php.

If one wishes those items to stick, one had better hunker down with the
browser and edit them by hand, each one.

Go ahead, run the below, note the effects, then run update.php. The
effects are then gone.

echo -n - > $t
php importTextFile.php --title MediaWiki:Privacy $t
cat > $t <<EOF

  • navigation
    • mainpage|mainpage
    • portal-url|portal
    • currentevents-url|currentevents
    • recentchanges-url|recentchanges
    • randompage-url|randompage
    • helppage|help

php importTextFile.php --title MediaWiki:Sidebar $t

Too bad there's no way to set them via LocalSettings.php.
No URL as this wiki is offline.

Version: 1.9.x
Severity: minor
OS: Linux
Platform: PC



Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 9:32 PM
bzimport added a project: MediaWiki-Parser.
bzimport set Reference to bz8975.
bzimport added a subscriber: Unknown Object (MLST).

robchur wrote:

Is the edit being attributed to "MediaWiki default"? If so, then update.php will
delete it as part of the message cache alterations shipped from 1.9.0 onwards.
In this case, use the --user option passed to the import script to attribute the
edit to someone else.

It would probably be wise not to use 'MediaWiki default' as the default username
for importTextFile, since that's intended to be used for things created by the
installer (and thus which can be udpated or removed with impunity).