Hmm.....playing around a bit, I now get the following errors:
exception 'missing_option_exception' with message 'Missing required option: dataroot' in mdeploy.php:363 Stack trace: #0 mdeploy.php(157): input_manager->get_required_option('dataroot') #1 mdeploy.php(838): input_manager->get_option('dataroot') #2 mdeploy.php(714): worker->authorize() #3 mdeploy.php(1399): worker->execute() #4 {main}
Hmmm ... that looks like you figured out how to execute the php file via command line. Am I guessing right? Did you execute giving the dataroot parameter?
The 'missing required option' is for dataroot ... which one can find in the config.php file of the site.
Would think, also, that this script must have access rights to be able to write to moodledata/temp/somedirectory (where is might unzip the package) and to the moodle code directory and then the mod/block or whatever the update notification is about.
Maybe a little more info is necessary ... updating a plugin could be core or an add-on. Are we talking the inability to update an add-on? If so, which add-on? Those are third party 'contributions', I think, is that the term is as shown on the update plugins form. Does it say an update is available for a contribution and then provides a link to download? I've see some like that ... not updatable via Moodle GUI and was provided a link to download the upgrade for the mod/block.
Got any 'secure' logs which might complain about apache user attempting to write to a folder?
'spirit of sharing', Ken
I've got this same issue. I upgraded our site to 2.6.2 20140310 this week and now I can't update anything using the auto option from inside Moodle. First I get that blank white page, and if I refresh it, I get that same error that was posted here. Uploading the files via ftp and then refreshing the notifications page is the only way I can update anything. I'd love to know what might be the cause so I can try to fix it.
Here's the error:
exception 'missing_option_exception' with message 'Missing required option: dataroot' in mdeploy.php:389
Stack trace:
#0 mdeploy.php(183): input_manager->get_required_option('dataroot')
#1 mdeploy.php(918): input_manager->get_option('dataroot')
#2 mdeploy.php(740): worker->authorize()
#3 mdeploy.php(1535): worker->execute()
#4 {main}
Hi folks
I'm getting a similar error to Brian in 2.2.4+, upgraded from 2.2.2+ 24th July
Linux Mint Petra (16)
MySQL 5.5.37
PHP PHP 5.5.3
debug info:
am getting same error here. in addition of missing "install button' ;
I have tried this
1- supplying dataroot parameter via command line using
$ sudo -u apache php mdeploy.php [options]. // it didnt change anything
2- enabled updateautodeploy in moodle GUI
3- added this line $CFG->disableupdateautodeploy = false; to config.php
4- changed file permissons of mdeploy.php to 777, temporarily.
5- edited the mdeploy.php and manually inserted the values of
$dataroot = 'PATH/TO/MOODLEDATA'; // after doing this , error changed to 'Missing required option: passfile'
$passfile = 'PATH/TO/PASSFILE'; // after doing this , error changed to 'Missing required option: password'
$password = 'ADMINPASSORD'; // the page went blank from here
am i missing something here?
https://docs.moodle.org/dev/Automatic_updates_deployment - case 3
Can't be done; the link is to development docs. The functionality still hasn't been realised.
I am getting this same issue. I am running 2.4.0. Is this really a non-functional item? The 2.4 docs say you can do this.
I am running 2.4 and attempted to auto-update a plugin and I get the error from mdeploy about "missing option exception" as shown in the picture a few replies above this reply.
I have attempted to update three different plug-ins: Face-to-Face, Certificate, and Open Meetings. All three give the blank page and then a refresh gives the error message. We are planning an upgrade to 2.8.3 as soon as our VM is allocated. I was just trying this feature.
So I guess I will have to wait. ...
All three give the blank page and then a refresh gives the error message.
Aha. Ok. As I was trying to explain above, that error is expected on refresh. It's part of the authentication and authorization process there.
We have to focus on why you are getting that (first) blank page. Blank page is typically a result of some PHP error in combination with displaying errors off. Usually, these errors are still logged in an error log file on the server (depending on your web server configuration). Can you monitor and check those?
