Easy way to duplicate/clone a placeholder.domain.com structure and content ?

same issue here. subscribing..

Not really, but then, I don't exactly understand the request, since your primary domain essentially _is_ a placeholder domain that is cloned when a new domain is created. All that remains is to assign content to the new domain, which happens automatically for content sent to "all affiliates."

Is the issue that you want a non-primary domain to serve as the template?

[Removing unhelpful tags. Please see http://drupal.org/node/1023102 ]

Hello Sir Ken!

Maybe we could have some way to "automate" this process. If you don't mind here's a little about the site I'm working now, and I'm using Domain Access http://groups.drupal.org/node/155359. To achieve this, I'm looking for some way similar or close to Anticosti suggested.

Looking forward for your help.

I'm sorry, but _what process_? Why is building off the primary domain insufficient?

So what you essentially want to do is the following:

-- Create a new, potentially "inactive" domain, for use as a source for new domains.

-- On adding a new domain, have the ability to "clone" any domain as a "source".

-- Cloning consists of the following:

* Copying all settings from the source domain (theme, etc.)
* Publishing all content from the source domain to the new domain.

You don't need to use node clone _unless_ you want different copies of the source nodes on the new domain. If you just want an existing node to appear on the new domain, the core DA module handles that already.

This is theoretically possible now, but it requires code and, frankly, a custom or new module. One would, I suppose, do the following:

* Expose a "source domain" field on domain creation.
* Use hook_domain_insert() to fire the necessary actions based on the source domain. These are likely:
-- Copy {domain_conf} to the new domain.
-- Add the new domain to any nodes assigned to the source domain.

Not sure if you want to add users as well.

This is definitely a new feature, and something that should be supported by the API. But it would go in a new module because this use-case doesn't fit the core purpose of the module.

sub

Sub as well.

subscribe