With the 7.x-1.18 arrival of Hook Update Deploy Tools for WordPress upkeep support plans 7 it is currently conceivable to trade a hub on an advancement sandbox, submit the fare record to the vault, then, at that point import it utilizing either a hook_update_N() or utilizing drush website convey import hub
Aces:
No compelling reason to re-make a hub on goad after a customer endorses it.
Early content that continues to get cleared out by information base snapshots (think style guides) can get re-made quickly with a solitary drush order.
Content imported into a current hub appears as a correction.
Atomated sending is testable and repeatable on all dev conditions.
No uuid required.
Work process Example:
You have a styleguide you made on your sandbox and need to convey it to the creation site.
Make the hub on your sandbox (hub id = 1234).
Fare the hub to a fare record.
drush site-convey send out 1234
The order made a fare record named for the false name of the hub being sent out
ex: site-convey/node_source/helpzZzstyle-guide.txt (‘zZz’ addresses ‘/’)
Make a hook_update_N() to import the record on arrangement
<?php/** * Import a the style guide */work site_deploy_update_7129() { $nodes = array(‘help/style-guide’); $message = HookUpdateDeployToolsNodes::import($nodes); return $message;}?>
Submit the document and update snare to your repo.
Push the code, run ‘drush updb’
drush updb – ySite_deploy 7129 Import a the style guide
Site_deploy: Updated: hub/1234: help/style-guide – successful.Summary: Imported Nodes 1/1. Completed the following: [help/style-guide] => Updated: hub/1234 Performed update: site_deploy_update_7129
or then again the import can be performed by
drush site-convey import help/style-guide
Source: New feed