Hello,
Before to creating version 2 of his web site, a customer ask me to create a second database, because he wants to be able to understand, to find, to export this specific content type (training). This user is a computer scientist of this company.
This request comes since he watched the drupal 7 database, and with his database background, he found the database organisation very complicated.
This guy doesn't want to understand very well how Drupal works, but he wants a system that he knows.
I mean, I could very well be wrong, but I just get this feeling that, as far as module development goes, Drupal 7 is the redheaded stepchild of the Drupal family. There is this massive body of work on pretty much everything I actually want to have... like large expanded user profiles and lots of user content and user relationships... and it all just ends at Drupal 6.
With Drupal 8 around the corner, is choosing whether to use a multi-site with a single code base, more or less appealing?
I've used Drupal 6 multisite with a single code base, as it makes keeping the core up to date, much easier. The only downside is having to put each site into maintenance mode, and run update.php for each one, made easier using the Drupal Remote Dashboard module (and corresponding Server).
For a migration form Drupal 6 to 7 or migration from traditional website to Drupal what is a typical engagement time lets say for 30 page web site?? and usually how many bodies would it involve. of course I do understand it depends on the complexity of the sites however is there a typical on what the community sees in the industry??
Thanks very much