Drupal Upgrade

I had met a peculiar Apache 2 error on Drupal upgrading. I can see my site loaded but can't access any of the sub-URL's in the site. When I provide the Url:www.test.com/admin/node, its shows "Requested URL /admin/node not found on this server". But if the url is provided like 'test.com/?q=node/', it allows to get the link.

Syncing means importing all files, permissions and data's from master to the development site, so that we have a two copies of live sites to test our new developments. In Drupal, its very easy to create versions of websites using this syncing process. Once the site is live to Production, the above process helps to fetch the sites data in the current scenario and to update few more features in the live site. I had a task to sync live database to development site's and came across some issues while syncing live database with the dev database.

Drupal 6 will be maintained till the release of Drupal 8. Drupal 8 release is expected to happen towards the end of 2013. The current stable branch Drupal 7 will be maintained till the release of Drupal 9 (probably 2015). If you are running a production site on Drupal 6 then you will probably have to start looking at upgrading the site by the end of this year.

Upgrading Drupal 6 to Drupal 7 is supposed to be a straightforward process but there are certain things you have to be careful about when you upgrade Drupal. The following list outlines the different steps you will have to follow to upgrade your non-mission-critical small Drupal site.

With Drupal 8 in the works a lot of Drupal 6 sites are currently upgrading to Drupal 7. We get quite a few queries on Drupal upgrades and almost everybody asks for a fixed price estimate for the process. In theory Drupal 6 to Drupal 7 upgrade process is an automated process (except for the upgrade of theme and custom modules) and all you have to do is to take the site through a set of standard steps for the upgrade. However upgrades don't always work like that.

Ecommerce used to be the preferred ecommerce solution for Drupal before Ubercart came into the picture. We recently worked on upgrading a Drupal 5 site with Ecommerce to Drupal 7 with Ubercart. The challenge with this upgrade was that the source data existed only in the D5 database and the corresponding code to programmatically access the ecommerce data was in D5 as well while the destination tables existed only in the D7 database with the corresponding code existing only in the D7 database. The solution we went with was to go for a full SQL query based migration to copy over the Ecommerce data from its tables to the Ubercart tables.