Deploy is amazing! :) After getting basic nodes working, I spent many hours trying to figure out why files were not working with Deploy, combed through issue queues, tested dev versions, etc. I eventually dug around enough in the code to find where the file was being encoded and figured out that the code was not running, and from there figured out that it was because hook_deploy_entity_alter() was never being invoked.
I rolled back to just before d64d5b8 and everything worked fine, and I was able to determine that the issue was introduced there, but only for new installs. For existing installs dependency_plugin will be empty and DeployIterator will be used unless you go in and re-save your plan configuration, then dependency_plugin will be default_iterator and you'll be stuck, UI-wise.
Add DeployIterator as an option for the dependency plugin via hook_entity_dependency_iterator(). It ends up being the first item in the dropdown and this looks to effectively make it the default.
Patch needs review.
Addition of a "Deploy Iterator" option to the Dependency plugin dropdown.
n/a
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | deploy-2290059-1.patch | 713 bytes | star-szr |
| deploy_default_iterator.png | 17.65 KB | star-szr |
Comments
Comment #1
star-szrHere's a patch, feedback please!
Comment #2
star-szrFixing commit link.
Comment #3
star-szrClarifying that this can also affect existing installs if a user goes in and re-saves the plan configuration.
Comment #4
fearlsgroove commentedThanks, I burned about two hours trying to figure out why all my entities where deploying with ids instead of UUIDs. Patch looks fine to me and fixes my problem.
I think there's more to be done around this -- is there a use case for the default entity dependency iterator to be available, since it doesn't have UUIDS? I'm setting RTBC under the assumption module devs have a longer term plan here, and this patch makes the current -dev versions usable.
Comment #5
star-szrThanks @fearlsgroove!
Comment #6
chrinor2002 commentedAny news on when this will end up in the dev version?
Comment #7
decipheredThanks @cottser, equally wasted time figuring out this issue.
Renaming this issue to make it a little clearer, because when the File deployment isn't working it's unlikely someone will search for DeployIterator (I know I didn't).
Comment #8
lisa.rae commentedTested patch from #1 above, works as described.
Comment #10
dixon_Thanks everyone for working and testing this one!
Committed to 7.x-2.x. A new release should not be too far away.
Comment #12
joseph.olstadPosting this because I spent a day scrambling until I found 'deploy_plus' to do bulk file deployment with admin_views.
For bulk operation file deployment the super easy way:
admin/structure/views/view/admin_views_filesee illustration:
" Manage entity in deployment plan "
It is easiest to do it with the built in capabilities of deploy_plus as I described above.
IMHO, deploy_plus works so well, it should be included as a sub-module to deploy.. However for now its a separate module that depends on deploy.
Alternatively, if you want to do it the harder way with rules (possibly without deploy_plus) , that works too, you can make a custom rule and then select it in views bulk operations, however why do this when you can just enable deploy_plus? More info about rules in the video below:
https://drupalize.me/videos/using-rules-components-vbo?p=1157