Drupal Blogs, Pictures, and more on WordPress: Migrating Drupal 6 CCK Programmatically – Add New Fields
Here is a method for adding new CCK fields to an existing content types and distributing those changes to multiple environments. See previous post for adding an entire content type.
Install the Install Profile API module from http://drupal.org/project/install_profile_api.
Drupal Blogs, Pictures, and more on WordPress: Modalbox comparison
Drupal Blogs, Pictures, and more on WordPress: Installieren von Blogger Templates / Bilder II
Eine Wahlmöglichkeit zu Picasa stellt ImageShack dar. Es bietet auch ein kostenfreies Service ohne Registrierung. Einerseits unterstützt der Template Generator das kostenfreie Service andererseits auch ein bezahltes ImageShack-Acoount. Für den Fall, Sie haben eine bezahlten ImageShack-Account, müssen Ihre Login-Daten in den Layout Generator eingegeben werden, damit eine bessere Blog Performance erreicht wird.
Drupal Blogs, Pictures, and more on WordPress: Drupal 7 Gotchas- Title not visible in "Add form" page AND Custom Node Not Visible in the "Content Types Edit Structure" page.
So I had implemented hook_node_info wherein I had specified the “has_title” as TRUE, but inspite of that I could not see the Title Field in the “add node” form and also I could not see my custom content type listed in the content types “edit structure” page. This being despite the fact that I had also implemented hook_node_form
After much ado I realized that I had specified a “base” in hook_node_info which was different from my module name. But I had implemented hook_node_form using my module name and NOT the base name.
Therein lied my fault.
Drupal Blogs, Pictures, and more on WordPress: Migrating Drupal 6 CCK Programmatically - New Node Types
CCK allows you to add custom content (node) types to Drupal. However, there is no automated method for migrating these content types to multiple environments, such as local developer machines, integration, quality assurance, staging and production servers.
CCK offers a manually executed export/import process, located at /admin/content/types/export. This works well for migrating from one environment to another. However, this process is time consuming and difficult to track when dealing with multiple target environments running different versions of your node types.
Here is a method for executing these updates programmatically. Updates are stored in a custom module install file and are implemented whenever an environment updates to the latest code base and runs update.php.
Install the Install Profile API module from http://drupal.org/project/install_profile_api.
Perform these steps for each content type to add.
Flickr: Open Atrium goes Kit compliant in 1.0 Beta 8 release
DevelopmentSeed posted a photo:
