People have applied the Migrate module in many different contexts, using it in different ways. Fortunately, some have taken the time to share their experiences:
- Getting it into Drupal with Migrate - Andrew Morton's presentation at DrupalCon Denver
- Data Migration into Drupal - video of Moshe Weitzman's DrupalCon London presentation
- Upgrade from Drupal 6 to Drupal 7 with Migrate 2 (blog + code)
- Migrating content by using the migrate module - btmash (blog)
- Migrating Content Part 2: Nodes - btmash (blog)
- Content migration using the Migrate module - btmash (presentation)
- The Economist.com data migration to Drupal - moshe weitzman (Drupal showcase)
I'm leading several non-profits and realized I need to do some web development now that our sites are actually getting some hits.
I'm hosted at Powweb (I've read they have terrible Drupal support) and just found out that my server has PHP 4.4.9. I want to say with Powweb, can I make this work out or probably not?
I would like to have one big happy Drupal multi-site installation via subdirectories.
However, it only sort of works. The premise is drupal is installed in a subdirectory of the webroot, not in the webroot itself.
I have followed the steps to create an appropriately named subdirectory in the sites folder. Now I have ....
I have told the sites.php about this site.
myserver.com/drupal/subsite ... myserver.com/drupal/subsite.myserver.com
myserver.com/drupal is still working.
myserver.com/drupal/subsite looks like it works, but it really doesn't.
Subsite as it works now looks a little like the default site, but the main content is fnf. Both are issues. I want to make subsite unique both in look and content.
When I try to administer the subsite, it looks like all of the urls eventually end up modifying the main site, not my subsite.
**When I set this up, I used the method of creating a symlink to the default site, so it could pick up the index.php. The database that drupal created for the subsite has about half the number of tables as the main site. I thought maybe that's intended, but can find no information to say yea or nay.
So I am stuck in Gondwanaland. It's all basically the same, but a little different. Please help!
I'm building a site for the fire department I work for. The site will include policies and bulletins that will be managed by multiple users. I'd like to create a block on the front page that lists any newly added or updated bulletins for a period of time, then automatically drops off the list. Is this something I can do in views?
I'm looking to migrate from my current website (D6), to one that I have already built (D7). In any proposal please provide a cost estimate, a timeline of work, and your soonest start date available. Relevant work experience would also be appreciated. To contact me, please use my email below.
My current site has ~400 users ~600 nodes
On the new site (D7) I am using entity fields for the user profile instead of the profile module in (D6). I want my nodes to retain their title, body, author and published date. Other node fields do not need to be retained. For my users I want to retain all their profile fields.
If necessary for your initial proposal I can create a D6 to D7 field map for users and nodes.