Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By Dr. DOT on
Running 6.14 -- all modules are up-to-date
Running Domain Access 6.x-2.1
Still cannot get a site to work.
Installed Drupal at http://our.domain.con/drupal
Created another host on the server http://another.domain.com
Trying to convert all pages over form live site to new Drupal site at http://another.domain.com
When I create a page and click Home > Administer > Site building > "new domain" I get the Firefox can't load this page... and the URL is http://another.domain.com/drupal/?q=admin/build/domain/view
If I go to the Home Page I converted at http://another.domain.com/ the Home Page loads fine.
Is there anyone out there with Domain Access experience that is able get multiple domains working under a single Drupal core install?
Comments
We have a site using domain
We have a site using domain access and after migrating from a dev url to a stage/live url we have to manually update the database. I'm not sure if this is the issue you are having, but here are my notes on what do in case it helps.
Log into the database and query:
select * from variable where name like 'domain_root'Then update the returned rows with the new domain. I think there is only one.
Then update any subdomains in the domain table. Sorry I don't have the specific name for the subdomain rows in the database right now, but you could find them by searching for your old subdomain.
Do something like
select * from variable where value like 'OLDDOMAIN'You may have to tweak that query a bit.
Ezra Wolfe
DLC Solutions
EthosCE
Thanks Ezra. I'll give it a
Thanks Ezra. I'll give it a try shortly.
I went into the tables to see
I went into the tables to see what is defined there. After looking (querying) I hesitate to change anything. Here is the reason:
The variable table's domain_root row has the value s:23:"abc.our.domain.com"; which is the correct domain root for our server.*
The domain tables' domain_id "0" row has the subdomain abc.our.domain.com, and
the domain tables' domain_id "2" row has the subdomain another.domain.com
I can log into Drupal core and do the things I expect to be able to do (at least at this juncture of my proficiency with Drupal). Yet, when I go to http://another.domain.com the only thing I can do is see the home page. I cannot do anything else beyond that -- can't navigate to other pages, etc.
*We have installed Drupal under abc.our.domain.com as drupal, so our core install is actually located at http://abc.our.domain.com/drupal
I do not want to have to change the newly converted website into http://another.domain.com/drupal because it is a mature website and many people have bookmarks out there and the search engines recognize the site without the /drupalk directory. So I do want to mess up our Web Analytics either.
Do you think I should change the variable table's domain_root row value to s:23:"abc.our.domain.com/drupal"; or s:23:"abc.our.domain.com/drupal/";? Is that where the problem is?
Those settings seem correct
Those settings seem correct to me.
I think that you have the issue right and there needs to be consistency between the two sites. It seems right that having one need /drupal and the other not is the cause of the problem. You might be able to make this work with an entry in your .htaccess file that does a rewrite.
Another suggestion would be, can you point the virtual host file in apache for abc.our.domain.com at abc.our.domain.com/drupal on the file system? That way Drupal wouldn't know or care that's it's parent directory was a subdirectory of abc.our.domain.com? Like this:
ServerName abc.our.domain.com
DocumentRoot /path/to/abc.our.domain.com/drupal/
etc.....
etc....
Or do you have other non-Drupal items at the root you need to keep available?
You might also post an issue on the domain access issue queue and/or search there if you haven't already.
Ezra Wolfe
DLC Solutions
EthosCE
Somehow this may need to
Somehow this may need to solved through mod_rewrite. But I am not very proficient with it.
Re: your comment on posting to the Domain Access forum queue -- I have been at this issue (Domain Access) for months. Most of my posts go without a response.
I can't redirect the document root because it is a shared server for virtual hosting and we have nearly 100 free standing sites on this server. That is why I elected to install Drupal under the /drupal directory hoping it would work as a single code install with multi-site capabilities. So far, it is proving to be anything but.
Over time, it is our plan to convert most sites to Drupal when and where it makes sense from an end user CMS perspective. Currently our users have Contribute but we want a better and more powerful CMS --that is one reason we are looking at Drupal.
Unfortunately, Drupal is extremely hard to get your head around and there is little support and hardly any concise and consolidated documentation (aka "an open source solution"). I realize there is documentation out there but it is so fragmented and module-centric that one hardly knows where to look to work through a problem. The forum could be a useful resource but I think for bigger issues like this one, most people shy away.