Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
So, when we set up DA, we did not use *.domain.com in cpanel. We just manually created only the subdomains we needed. Now that we created a whole new account using WHM, say, newsub.domain.com. Even when there is other content inside, it still shows content from domain.com (where DA + D6 was insatlled). Is there a way to disable this behavior so that newsub.domain.com would not be controlled by DA anymore?
Comments
Comment #1
theroyal CreditAttribution: theroyal commentedDid you try to check but with different account other than (user:1) ?
Comment #2
jweirather CreditAttribution: jweirather commentedI'm not sure I'm understanding, but it sounds like you have a new web folder/database "newsub.domain.com" that should be completely separate from an existing drupal install, but traffic is still being forwarded to the old install? And probably to the default domain's content?
If so, my gut feeling is that the problem is actually with DNS or with the folder assignment in cpanel/whm. My guess is that you have you DNS records controlled by the same cpanel account as the original install? If so, you may need to add an A record to that DNS server for newsub.domain.com that points to the ip address of the new installation. Also make sure that, at the new destination, the IP traffic for that subdomain is forwarded to the correct folder.