Extension talk:MaintenanceShell/Archive

It works fine on Mediawiki 1.14.0. Thanks! Enzo // Same on 1.13.4. Al Maghi

Hey, great idea! Exactly what i was looking for to run on my rather restricted server. stupid university sysadmins :(

I dunno if this discussion page is the right place to post this, but nevermind.

I think I found some minor glitches:


 * MaintenanceShell_body.php, line 50: the & and ? are in the wrong order, swap them in order to get the list of maintenance scripts on Special:MaintenanceShell functional again
 * MaintenanceShell.php, line 41: it should say 'Location: http:// ', otherwise it renders the URL unusable
 * MaintenanceShell.php, line 50: this looks like a remainder of v0.1.0's password system to me?

Unfortunately I could not get it to run. After filling the form with, let's say checkImages and command line "--fix" and submitting, the script just returns to Special:MaintenanceShell without any further ado...

Any ideas? Any Feedback would be greatly appreciated. Please mail me in an electronically manner to user PHIL at the hostname METAPHIL in country DE :-)
 * Hi Phil.. sorry it didn't work for you.. I'm not sure why. I will look into the bugs you posted.  I really appreciate your feedback and hopefully we'll get it working for you :) What version of MediaWiki are you using?  I can only verify it should work on 1.14.0  --Frantik 23:13, 31 May 2009 (UTC)
 * I followed up with Phil and I think we've got his problem solved... The user rights must be placed before the script call. --Frantik 19:55, 1 June 2009 (UTC)
 * v0.2.1 addresses the bugs mentioned above --Frantik 02:57, 2 June 2009 (UTC)

Stupid question but where do you actually go to use MaintenanceShell once installed?--86.28.134.69 11:27, 4 June 2009 (UTC)
 * Thats a great question actually lol.. you can see it on Special:SpecialPages under Wiki data and tools, or its own page Special:MaintenanceShell --Frantik 00:55, 5 June 2009 (UTC)

I installed this on 1.13 and was executing the skin change command: userOptions.php skin --old "monobook" --new "modern" It executed and it stated that it actually performed the action. However, when I went into the accounts to check, it actually didn't work. The user skin was not changed. Could it be an issue with writing to the database? Why would it say it completed OK if it didn't make any database changes?--Valiot 11:11, 18 July 2009 (UTC)
 * Hi, I didn't notice your comment. Unfortunately I can't give help on the individual scripts, I've only created the interface to access them.  Honestly I don't even know what half of them do!  --Frantik 17:19, 15 August 2009 (UTC)

How to get a NULL setting ? ( "" or ' ' not working)
I run the command  php userOptions.php gadget-HotCat --new 1 --old  ''

Result:

''The script is about to change the skin for ALL USERS in the database. Users with option =  will be made to use '1'.

but it doesn't get the NULL setting from old ''. Doesn't work either with old "".

--almaghi 10:09, 10 June 2009 (UTC)
 * I'm not 100% sure.. does this command work as expected from the command line? (though I assume you're using this extension because you can't access the command line) --Frantik 19:47, 11 June 2009 (UTC)
 * Ok it seems I'm not handling quote marks properly. i will update it --Frantik 19:51, 11 June 2009 (UTC)
 * Yeah it does work as expected from command line. --almaghi 15:47, 15 June 2009 (UTC)
 * Ok. Thks for your update & your extension, good job is done here ! --almaghi 15:47, 15 June 2009 (UTC)
 * Thanks! I will release the update soon :) --Frantik 00:21, 16 June 2009 (UTC)
 * v0.2.2 should solve this issue :) --Frantik 01:14, 19 June 2009 (UTC)
 * v0.2.2 test: The " " works, it give a NULL value. The  ' '  doesn't work. I think this last bug is not inconvenient: when  ' '  doesn't work the first idea that come is to test with " ". --almaghi 08:32, 19 June 2009 (UTC)
 * cool, that is expected. I will add support for single quotes next time.  Glad to know it works --Frantik 08:56, 19 June 2009 (UTC)

Working directories
Hi, I want to use maintenanceShell to install FlaggedRevs and for this, i need to change the working dir to something like /wiki/maintenance/archives/ and to /wiki/extensions/FlaggedRevs/ to get the scripts from there.

Where and how should change the $wgMaintenanceShellDir ?
 * You set it in your LocalSettings.php file. Right now the script doesn't support Maintenance shell scripts outside of the mainenance folder. --Frantik 16:41, 31 July 2009 (UTC)
 * The easiest way to run scripts in those other folders is to copy them into the main maintenance folder. the next version I release will support the subfolders --Frantik 15:20, 10 August 2009 (UTC)

file_exists Error
I'm trying to run  in MaintenanceShell (without any arguments at this stage) and get the following error:   --Agrestis 09:49, 6 October 2009 (UTC)
 * this is an error in commandLine.inc (not part of my extension).. it seems like it's left over from Wikipedia since it's referencing a specific file. You can safely ignore it as it has no effect on the actual maintenance scripts --Frantik 05:04, 12 October 2009 (UTC)
 * btw, are you using 15.1? i noticed i had to do another tweak to get this extension to work on 15.1 so i need to release an update --Frantik 05:08, 12 October 2009 (UTC)
 * Thanks, I wasn't sure if the error was the extension or Mediawiki itself. For reference I'm using Mediawiki 1.14.0 with MaintenanceShell 0.2.2 --Agrestis 19:51, 12 October 2009 (UTC)

PHP Notice: Undefined index: extension in /var/www/html/extensions/MaintenanceShell/MaintenanceShell_body.php on line 58, referer: http://wikiserver/Special:MaintenanceShell
replace line 58 in maintenanceshell_body.php with {	if (($arr = pathinfo($v)) && array_key_exists('extension', $arr) && ($arr['extension'] == 'php') && (strpos($v, '.inc') === false))

i believe this is being caused by the sub directories in this folder or possibly some of the files that do not have extensions.
 * oops.. thanks for the heads up on that one --Frantik 14:25, 14 November 2009 (UTC)

nice
Installed and works nice. Two suggestions, though. Change the folders name. It's confusing and would save the extra step of changing it after the wiki goes off because something's wrong in localsettings. And two... can you specify more clearly how to use options. if you're using -r, for example, you just wrote -r or something else is needed? You mentioned something about using quotes in the main page. Other than this, kudos. Really usefull tool for all mediawikians.--Mark 03:45, 11 December 2009 (UTC)
 * A couple more things: The go back to maintenance shell is broken in Spanish (and probably other languages). In the Spanish case the link is to "Especial:". Also, for those using shared hosting, you need to set up your AdminSettings.php with the password and login to your database. Some scripts are timing out, but I'm still testing. Will be back here. --Mark 04:15, 11 December 2009 (UTC)
 * Refresh Links script times out in about a minute+. This is the message.

Refreshing links table. Starting from page_id 0 of 13706. 0 ï»¿100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 ï»¿1400 1500 --Mark 04:24, 11 December 2009 (UTC)
 * checkUserNames doesn't run at all.--Mark 08:14, 11 December 2009 (UTC)
 * Hi Mark - this extension is mostly just a wrapper, I can't really provide help on how to use the various scripts or even guarantee all scripts work correctly. I will look into checkusernames when I get a chance.  --Frantik 11:03, 16 December 2009 (UTC)

"Return to Maintenance Shell" bug
On the "run script" page, there is a link to "Return to the Maintenance Shell". That link is busted...it points to "index.php&title=Special:MaintenanceShell". It should be a question mark instead of an ampersand before the "title" parameter. --Duke33 19:57, 16 December 2009 (UTC)
 * thanks, this has been corrected for the next release --Frantik 00:15, 17 December 2009 (UTC)

Recaptcha bug
If Extension:reCAPTCHA is installed you get the following message when trying to run any maintanance script: "You need to set $recaptcha_private_key and $recaptcha_public_key in LocalSettings.php to use the reCAPTCHA plugin. You can sign up for a key here." Those lines are of course present and reCAPTCHA works fine everywhere else, so probably something about the way this script is calling others.