Drupal Migration - Onion Skin, or Per-node?

A few words about the Migrate module. Migrate module is a powerful tool that allows to move content from other CMS into Drupal. Migrate module allows you to map sources to Drupal destinations, and import them in a batch script. Currently, there is support for pages (nodes), categories and tags (taxonomy), media (images, audios and videos), addresses and geodata, and field collections. Some pieces of content work out of the box, some require additional modules (like migrate_extras), and some require patches (field collections). Migrate module is the most powerful of existing tools to handle complex sites and supports multiple source formats, most common being database and xml.

Now to the point. There are two basic ways to import complex data. One is an "onion-skin" migration, and another is a per-node type.

Save/update field collection without node_save

Some sites are quite complex. And some complex sites also have complex pages. A good way to group data on those pages is to use Field Collection module. Field Collection module utilizes Drupal 7's entity interface to store your field collection as an entity, rather than a field directly attached to your node. The benefit is obvious - you can manage little 'sub-nodes' for your node, like company's houses, or person's quotes, without having to create a whole new node for them. And for multi-value field groups, it's just a prodigy!

DigitalOcean $5/mo server... uh... $10/mo server.

I have been searching for something like that for a long time - a service that is cheaper than Rackspace and Linode, and no traffic fee. It's high time, if you ask me - RAM costs coppers these days. Such servers are great for testing purposes, and sandboxes for clients. But such services usually have some cons as well. Here are some pros and cons of such hostings:

SiteHound Drupal available for download

After a long time of preparation and tuning, SiteHound has been made available for free download. At the same page, services can be purchased - including installation and customization. To honor the original Drupal's GNU GPL license, the package is shipped free under the same license.

Due to the fact that SiteHound is rather imported that installed, there is no installation page currently. Below is the content of the SiteHound readme file, shipped in the distribution archive:

SiteHound is a ready-made Drupal site, developed and packaged

SiteHound will Support Recolorable Themes

Sitehound Drupal is aiming to be as out-of the box as it can. Hence, it was my choice to add support for the Drupal's Color module (and SASS). There are currently 6 ready color variants in SiteHound standard theme, the default being the gray one. These color variants can be chosen in the theme settings section. This is also where a custom color set can be created with the Color module graphic interface.

SiteHound Idea Revived, Approaching Alpha

About a few years ago, I had worked on a pre-configured Drupal site, that can be used as a template for building client web sites. Now, I decided to revisit that idea with Drupal 7. Drupal has a steep learning curve, and comes with a need to have it configured before it can be used. WYSIWYG installed, content types added, image fields, galleries, layouts for pages.

Recoloring themes - the Color module

Using the Color module is easy - thought I could not understand how I can map colors to classes and id's . Which, I can't - you simply declare default colors, the themes colors, tell which css file to use, and then the Color module overrides default colors with counterparts throughout the whole theme. Good for recolorable themes.


Subscribe to RSS - blogs