When chosing "add to deployment plan" on the content admin page, the page reloads with node_operations/deploy/1 and shows a "Page not Found" error.
Also when I try "Deploy" from the update options, I get the deploy screen with the login information. When I fill out the info and hit submit, I get this error...
Module Description Result Message
login Remote user login Error Missing required arguments.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 702730-node-operations-404.patch | 4.52 KB | katbailey |
Comments
Comment #1
qbnflaco commenteddeploy_uuid_services wasn't enabled. I enabled it and now I don't get the "Page not found error" but I'm still getting...
Module Description Result Message
login Remote user login Error Missing required arguments.
on deploy.
I'll try a fresh install and see if this was just a fluke.
Comment #2
qbnflaco commentedhmm.. I tried on a local install and same thing...
Just to make sure, here are the modules I activated on the source site...
drush -y enable deploy deploy_uuid node_deploy deploy_uuid_service
I added the destination server, then I duplicated the site and on the cloned site enabled...
drush -y enable services_keyauth xmlrpc_server system_service node_service user_service deploy_uuid deploy_uuid_service
Tried to deploy a change to node/1 on the source server and I get the same thing. Am I missing something?
Comment #3
qbnflaco commentedok, figured it out... I had inversed the checkboxes and had keys checked and sessid unchecked. I fixed that and it's working perfectly now.
Comment #4
thinkling commentedI just ran into this too and to clarify: you have to have the Services Key Authentication module enabled & configured on the *source* server as well as the destination server. The handbook page on Deploy setup does not mention this.
Comment #5
add1sun commentedI've updated the handbook page to indicate you need key authentication on the source server and I added a section to the Basic Usage page about deployment plans http://drupal.org/node/408776.
Comment #6
isaac77 commentedYou may also need to clear your site's caches. I got "page not found" when adding nodes to a deployment plan until I used the flush caches command in the admin menu module. This may be obvious and not specific to this module, but it's easy to forget...
Comment #7
katbailey commentedNope, this behaviour is just plain lame and it is definitely a bug - if there's a dependency on another module, then the option to add nodes to a deployment plan should not show up without it. Should be an easy enough fix, assigning to myself.
Comment #8
katbailey commentedOK, so what was actually happening here was that the menu items for 'node_operations/deploy' and 'node/%node/deploy' were being defined conditionally, based on whether there were any existing plans. The menu does not get rebuilt when you create your first plan, so these menu items were never getting registered. The fact that it worked after enabling UUID Service is simply due to the face that the menu gets rebuilt when you install new modules - any module would have done ;-)
I'm attaching a patch that removes this conditional in the menu as it is completely unnecessary, we can deal with lack of plans elsewhere.
I will commit this shortly if nobody objects. I'll also remove the erroneous install instructions from the documentation - there is absolutely no need to have any of the services modules enabled on the source site.
Comment #9
katbailey commentedI just committed the above patch.