Tuesday, Aug 13, 2013
As a follow up to my previous post on Drupal 6 Post Migration Data Clean Up, I thought that a follow up for Drupal 7 would be useful. In this one I have also included the block_custom table for custom blocks, which seems to be a place I have overlooked before.
Update links inside node body and custom blocks: UPDATE `field_data_body` SET `body_value` = REPLACE(`body_value`, "http://[temporary site]", "http://[new URL]"); UPDATE `field_revision_body` SET `body_value` = REPLACE(`body_value`, "http://[temporary site]", "http://[new URL]"); UPDATE `block_custom` SET `body` = REPLACE(`body`, "http://[temporary site]", "http://[new URL]"); Update links to files/images within nodes and custom blocks: UPDATE `field_data_body` SET `body_value` = REPLACE(`body_value`, "sites/[temporary site]", "sites/[new URL]"); UPDATE `field_revision_body` SET `body_value` = REPLACE(`body_value`, "sites/[temporary site]", "sites/[new URL]"); UPDATE `block_custom` SET `body` = REPLACE(`body`, "sites/[temporary site]", "sites/[new URL]"); Another useful place if you are looking for post migration is to rebuild your sitemap (using xml_sitemap) and clear all the caches. ...
Thursday, Mar 15, 2012
Presented at Drupal Science Camp January 2012 in Cambridge.
Monday, Jun 13, 2011
Well this post has been a long time coming. Around 3 months ago I presented to Drupalcambs a presentation about extending the migrate module to enable you to map and import data using the fantastic migrate module. I say fantastic as the migrate module lets you do some awesome stuff when migrating.
Previously it had been hard to properly insert nodes (with files/taxonomies), taxonomy terms and users, however, utilising the new fields that Drupal 7 gives us has made it so much easier. ...
Thursday, Mar 31, 2011
Post migration data clean up, basically, most of the time when you develop a site you do it either under the default site of Drupal (sites/$new_url) or you do it under a different site (mynewsite.willhallonline.co.uk) with the intention of moving it to its own domain name when you have finished.
Moving your data when you have finished on your new site is pretty easy. As most of the parts of your data are in the database, you can almost move to any file location and providing it is in the drupal root you will be fine! ...
Wednesday, Mar 2, 2011
So, if you have missed it, Drupal 7 is stable (it has been since the start of January), and this means that more and more people are going to be looking at Drupal 7 both now an in the future to work as their content management system. Much of the work I do involves either migrating sites from other formats (CMSs, static sites or bespoke sites) into Drupal or importing of other data into Drupal to open the data to Drupals awesome data management and processing. ...
Sunday, Sep 5, 2010
I have been reading recently about developers giving realistic timescales to deliver projects in. I am well aware that developers can over and under estimate projects and also that you can spend a lot of time developing a project only for the idea to be changed just before the site is ready to be released. However with this in mind here is my Drupal migration timescale equation:
D + 12 + P + F = H ...
Thursday, Apr 15, 2010
After presenting on ‘Migration to Drupal’ on Monday 12th April at DrupalCambs, had a few good chats about the nature of the Drupal database and associated points.
Potentially, Migration to Drupal, I believe is fairly straighforward depending that you understand both the source and the target data well. Therefore in most cases you need to know your database and the Drupal MySql (or PostgreSql) database. However, for future reference it appears that when using content management systems, there is a belief that you don’t need to understand how the data interacts providing that it does. ...
Thursday, Mar 25, 2010
The migration of OsCommerce user to Drupal user can be a troublesome one, largely due to the password storage within OsCommerce. Ryan from Ubercart “the osCommerce method of storing passwords involves using “salt” on the password… appending some random characters and making an MD5 of it all. You can’t undo MD5 hashes to get the original password, unfortunately, and Drupal just uses an MD5 of the password itself” (http://www.ubercart.org/forum/development/1379/oscommerce_ubercart).
Therefore, the entirety of users to be migrated is tricky, however, a large amount of the details can be sent across as required. ...
Sunday, Mar 21, 2010
Following the uploading of products to one product database within phpmyadmin/mysql root, you will now have a Drupal database with a new table named ‘products’ within it. You can then use the table wizard module to expose the table to the migrate module and draw relationships between the ‘products’ and ‘uc_products’ database table.
I have added another little script which runs almost the same process as the migrate module, however, this may need to be edited to run successfully: ...
Saturday, Mar 20, 2010
The difficult thing that appears with moving the products using the migrate moduel appears to be the inability to put multiple tables into one table. To counteract this I ended up migrating all ot the Oscommerce product data into one database table and then sending the content over with the migrate module. The code ended up something like this although this is obviously editable dependant on what data you have in Oscommerce/want in Drupal: ...
Connect on LinkedIn. Follow me on Twitter. Grab the RSS Feed