By xurizaemon on

We have an existing Ubercart site which is focussed on our country, and want to roll out a matching copy of the site for a nearby country.

The aim is to have a single DB of product nodes (no duplicate product management) and still be flexible enough to have different text on the contact page for each region.

The regional sites will probably have slightly different themes and a custom module each for region-specific tweaks. I'm thinking that using shared tables for the nodes and Ubercart product tables will

I've investigated the Internationalization module but it seems that with it we'll end up with a new set of URLs (eg en-NZ/contact and en-AU/contact-0) instead of matching URLs. Otherwise, it seems pretty good - regional pages can be handled as "translations" and the default content can be English for anything which isn't region specific.

We also considered other options for replication, ie aggregation (pulling products in via RSS), UC import/export (appears to have had little active development since 2007), MySQL replication (doesn't allow for country-specific changes), database import/export (means having to duplicate logic to identify country-specific content outside Drupal). None of those appealed, but I'm all ears if you have a good idea.

This site is currently on D5, simply because there hasn't been a great need for us to migrate yet. That said, there are a few features which tempt towards D6, and I'd love to hear about D6 facilities which would make this need easier to resolve.

How would you implement this? If you've done it before, what worked, and what didn't?

⋅ Categories: Drupal 5.x