Closed (outdated)
Project:
Deploy - Content Staging
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
29 Sep 2010 at 07:12 UTC
Updated:
30 Sep 2016 at 15:12 UTC
Jump to comment: Most recent
Comments
Comment #1
dixon_It sounds like it's a regular node type you are trying to deploy? The Deploy module supports deploying content type with help from the Content Type Export module shipped with CCK. The configuration that is not covered by that export, won't be deployed, though. But that is a general Drupal/CCK problem rather than a Deploy problem.
To answer you other questions, all the most recent code is in CVS. I don't know about the status of the Git migration. But don't assume that repo is up to date until the whole migration for drupal.org is done.
Comment #2
joseph.olstadFile deployment (using the entity api they are entities of type 'file') works great.
see the related issue for details. In Drupal 7 it works great as I described in the related issue.
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