views:

198

answers:

3

Hi,

I am farmiar with building drupal sites but not sure what the best way to implement this scenario. I have two domain names mydomain.com and mydomain2.com. I need to have a conten type with some fields in. i.e.

ContentType
Field - Title
Field - Body
Field - Picture
Field - Price

I want both sites to use the same data for the custom conten type. So you enter the data on one site and it will be updated on both.

mydomain.com will show the follwoing infromation from the content type.

ContentType
Field - Title
Field - Body
Field - Picture

mydomain2.com will show all the data.

mydomain.com and mydomain2.com will have diffent look nd feel. And each domain may use some diffent modules. mydomain2.com will be using ubercart and mydomain.com will not.

Would I use mutlisite here and somehow sharte the tables. Use one instance of drupal and do the rest with theming? Use features and context?

Any help would be apreciated.

+2  A: 

After doing some research this may be what I need http://drupal.org/project/domain. A case study can be found at http://drupal.org/node/369398.

Still wondering if there are otherways so not acepting this as the answer yet.

Rupert
I agree, Domain Access has worked fine for me in similar situations. On the other hand: If all nodes will be published on both sites, and the *only* difference is going to be the theme and the hidden price field, Domain Access would be overkill. In that case, you could switch themes based on the domain name and hide the field with some simple custom code.
marcvangend
A: 

The Domain module looks good (although I haven't used it). It may be overkill for your needs.

If you want something very simple you can create a module which sets the global $custom_theme in hook_init() depending on the domain.

Jeremy French
A: 

For me, if this was a critical portion of the site, I would create a custom module. There are a few guides out there to create node_types through modules. I happen to like this one.

That way, you have a basic structure of your data in a custom table and then can customize the call for displaying the data to either include the price column or not.

Again, some may see this as too much work but if you aren't familiar with Drupal module development, this is a great way to learn. If you are familiar, it should be quick and simple.

Chris Ridenour

related questions