I have 2 D6 sites (primary.tld & subdom.primary.tld) which used to be part of a multisite (2 databases,1 code base) setup but I needed to split it into 2 database with 2 code bases.
Previously the primary site had a menu entry with a link to the subdom site to direct users there but my problem is that now instead of redirecting to the 2nd site my primary site reproduces all its content under the subdom's url and none of the subdom content is accessible.
e.g. primary.tld/aboutus will be called subdom.primary.tld/aboutus even when i never had a url like that on subdom
I've confirmed the subdom site db contains its data and its settings file points and connects to its database
I replaced the settings.php file in suddom/sites/default/ with a fresh copy from drupal default and added the db settings but that didn't correct the problem.
I also did the same for primary.tld/sites/default but no change
Both sides are on different file paths and different IP addresses
Comments
Hey, I don't know if I am the
Hey,
I don't know if I am the person that can help you with this but I did read your problem and I am still a bit unclear.
I'm guessing it is not as simple as going into the menu and manually fixing the links?
Perhaps you can give an example of howit SHOULD be working.
Did you edit the menu entry
Did you edit the menu entry for the aboutus link? Did it have a relative link like 'aboutus'? Or was it 'subdomain.primary.tld/aboutus'?
And do you have a module like Domain Access or Subdomain that's filling in a few blanks here and there?
Sorry I thought I had
Sorry I thought I had submitted a reply already.
Thanks to everyone for getting back to me.
Its not a menu link error because the URL is absolute and points to www.subdom.primary.tld and if I open www.subdom.primary.tld without first visiting the primary site I get all the primary sites content but under the www.subdom.primary.tld url.
Its like the primary d6 setup thinks it should respond to requests www.subdom.primary.tld and since it doesn;t have any of its content (because the subdom database is elsewhere) it serves up its own content instead.
I can't figure out how to browse or view any of the subdom content because even when I enter a url to subdom only content I get an friendly drupal error which looks to be generated by the primary d6 codebase, db and theme saying the file can't be found
Is there a way to verify that the primary drupal codebase is actually responding to requests for a website that is managed by a different account, on a different IP (shared) and uses a different url?
It looks like its 2
It looks like its 2 problem
1: the DNS entry for the subdom site needed to be changed cause the IP address had changed. That was probably why any requests were not even getting to subdom.primary after the split. I made the changes and the subdom site appeared
2: My primary d6 site looks like it will respond with a website directed at its IP address.
Is there a way to stop that from happening so it doesn't happen in the future?
Quoth: "2: My primary d6 site
Quoth: "2: My primary d6 site looks like it will respond with a website directed at its IP address.
Is there a way to stop that from happening so it doesn't happen in the future?"
The 'primary' site isn't really primary. It's the default site. So if you have siteA.com set up in sites/default, and siteB.com set up in sites/siteB.com, then siteA.com's settings will always be the fall-back if siteB.com doesn't work. If you don't want this to happen, set up a sites/siteA.com folder with siteA.com's settings, and then create a 'something bad happened' site in sites/default.
Hope this helps. :-)