Right now when deleting a domain, there are two options for the content held within that domain:
1. Reassign content to another domain.
2. Don't reassign content.

If you don't reassign the content, it will get co-mingled with the default domain. If you have a small site up for a short while with a couple hundred nodes, it could be a little problematic to chase them down to delete them. They also might not have any relation to the default or any other domain.

Would it be possible to add a third option to delete the content relating exclusively to that domain only?

Thanks Agent Rickard

Comments

MrPhilbert’s picture

O.K. I just found it.

Prior to deleting a domain (affiliate), go to affiliates and choose the affiliated content for that domain. Then batch delete.

Make sure you do this before deleting a domain or the content will be hard to find.

Philbert

agentrickard’s picture

This still sounds like a valid feature. Are you sure it isn't a duplicate?

MrPhilbert’s picture

It would be cool to add this to the domain delete page. If you did not know to delete the domain content first and just deleted the domain, you would end up with the deleted domains content in the default domain. Whew!

Right now I am building a web site as a volunteer (voteworkingclass.org) and will offer sub domains for different areas to organize. If one area closes, it's important to make sure that the content does not get co-mingled.

Philbert
P.S. As for duplicate, I tried to find anything relating to this in the issue cue first and could not find anything.

agentrickard’s picture

When deleting, how do you make that determination? Here's the challenge:

If the content is assigned to all affiliates, do you delete it?
If the content is assigned to multiple sites, do you delete it?

These two cases mostly apply when Domain Source is used. If you don't delete this content, you may have to re-assign it.

MrPhilbert’s picture

This seems to be similar to deleting a user.

I see in the affiliate content area, there is the option to move content from one domain to others. That was very well thought out.

Thanks.

I'll take what I am learning here and continue to add to the documentation.

dqd’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

I'll close this issue due to inactivity for 12 years and upcoming EOL of Drupal 7 in January 2025. While the project's version for Drupal 7 will surely keep providing support for security issues and website breaking bug fixes for Drupal 7, we should try to minimize the open issues for Drupal 7 in the queue as much as possible. A big thanks around for the report and all the efforts in here. Feel free to re-open if you can provide a fix or found an additional related problem which increases the issue priority.