Hi Folks,
I've got a fresh new installation of a mediawiki (1.6.10 for MySQL compatibility with other company apps) and I'm now in the process of writing a script which will pre-populate it with new (orphaned) pages using the importDump.php script. Because I know the exact scope of the use of this wiki, I have been able to pre-determine the exact number of additional namespaces and categories in advance.
My questions are:
1) From a fresh wiki, is it better to add the category and namespace data into the XML files before importing them and then running the maintenance/refreshLinks.php -- or -- is it better to set-up the wiki with the categories and namespaces first (using the LocalSettings.php file???). Or is there another 'best' way.
2) Also, I wish to "lock-down" the categories and namespaces to all users other than admins. What is the right way to do this?
Thanks folks! - Rich
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
revansx wrote:
I've got a fresh new installation of a mediawiki (1.6.10 for MySQL compatibility with other company apps)
1.6 through 1.10 have the same MySQL version requirements, as far as I know. (1.7 and later require *PHP* 5; 1.6 and later require *MySQL* 4.0.x or later..)
- From a fresh wiki, is it better to add the category and namespace
data into the XML files before importing them and then running the maintenance/refreshLinks.php -- or -- is it better to set-up the wiki with the categories and namespaces first (using the LocalSettings.php file???). Or is there another 'best' way.
There is no category data in LocalSettings.php; categories are created simply by use in a wiki page.
Namespaces must be set up in LocalSettings.php with $wgExtraNamespaces before they are used. If you have to add namespaces after importing data with importDump.php, you will need to run namespaceDupes.php to fix up the database entries.
- Also, I wish to "lock-down" the categories and namespaces to all
users other than admins. What is the right way to do this?
MediaWiki has no support for this. Unsupported hacks may exist which may or may not work, and may or may not contain security flaws which expose your protected data.
- -- brion vibber (brion @ wikimedia.org)
mediawiki-l@lists.wikimedia.org