----
ISSUE: Domain-5.x-1.0
----
Applied > multiple_node_access.patch: good
Applied >custom_url_rewrite_outbound.patch: good
Add to settings.php > custom_url_rewrite_outbound function.: good
Add to settings.php > domain_conf settings override: bad {error}
----
The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
This problem can sometimes be caused by disabling or refusing to accept cookies.
----
I can not get past this. I tried option 1 and option 2 with the same results. The error doesn't help me solve anything. It basically tells me nothing. I haven't seen anyone else with this issue. I checked to see if the code was correct and that the path was correct. I really need this feature, so I have to figure this out.
Does anyone know why this one thing isn't working? What could cause this type of error? Thanks.
----
SYSTEM DETAILS:
----
Drupal-5.6
MySQL-5.0.27
PHP-5.1.6
Server-Apache/2.2.6 (Fedora)
Godaddy Dedicated, Managed w/ Plesk-8.2.1
----
I can add this to the issue area in on Drupal.org as well, but I wait for advice on that. I'm a newbie and I am not really sure when to ask what where... Draupl.org feature request or issue or general discussion and then there is groups. I seem to find better more deatiled answers here... so... I posted here.
Thanks in advance any assistance you have to offer.
Mystical
Comments
Comment #1
agentrickardWhat the error tells you is that the web server keeps trying to load a page that, in turn, tells it to load the page. It's an infinite loop, so Firefox stops.
And when you remove the require_once code for Domain Conf from your settings.php file, this goes away?
Did you already configure the Domain module? The primary domain?
Do you have access to your server error logs? That will probably reveal the issue. My guess is that there is a server issue somewhere and the Domain Conf issue is not the problem, but merely reveals the actual issue.
Comment #2
agentrickardI will be offline for a few days, so hopefully the error log will show an obvious answer.
Comment #3
SeedTreeLLC commentedNo. I had tried to insert it before I installed. I added the lines after and reloaded. Then it tried to re install everything and warned me that it had already created the database tables. I hit the "back" function in the browser and it took back to a fully functioning tool. I turned on the Domain Conf and it seems to be working fine for now. Weird. I bet I couldn't duplicate the issue or the solution ever again. Sorry I didn't respond sooner. I had to run out and eat dinner and left in the middle of posting this.
Thanks for being so on top of things. You solved my issue with your first post. I must have missed the part about configuring the main module first, but I've been reading through tons of readme and install files.
~ Misty
Comment #4
SeedTreeLLC commentedOf course, I wrote to soon. I am getting it when I try to edit the settings on the settings or theme in any of the other domains. I'm misreading the install instructions. I hope I don't have to start over. I am going to reread the files again and try to see where I went wrong. Any other suggestions would be appreciated.
Comment #5
agentrickardThe problem likely comes down to how your subdomains are configured at the server level.
Remember that Domain Access does not handle DNS services in any way. Your server configuration needs to be pointing all of your host names to the same IP. I am not sure that you can do this through Plesk.
See also:
http://drupal.org/node/213278
http://drupal.org/node/203507
http://drupal.org/node/212915#comment-730839
And especially http://drupal.org/node/212915#comment-730883
Comment #6
SeedTreeLLC commentedYes you can add DNS records in Plesk. I have installed the Domain Module and had it working before. It was a different release. Maybe it is this new version. The last one (rc4) had a different patch file (I think). Am I suppose to load the Domain Conf with or after everything else? Shouldn't the settings.php file have the settings override code when I upload Drupal or am I doing this all out of order?
Comment #7
SeedTreeLLC commentedThese are the errors I get when I add the domain_conf settings override.
Comment #8
SeedTreeLLC commentedSo. What I didn't get from the instructions was that I needed to first do a full install of Drupal and Enable just Domain Module. Set everything in the site. Then add the Domain Conf to the settings.php. Then turn on the other sub modules. Anyhow, that is what I figured out. Sorry if it should have been obvious, but I didn't really see in the instructions to do it after.
Thanks.
Comment #9
agentrickardIt probably needs to be more clear. It's obvious to me, of course, but you should not have had to go through this.
Where should I add the documentation? In the main INSTALL file?
Comment #10
SeedTreeLLC commentedSince it prompts you to refer to the special install.txt in Domain Conf in the primary install instructions, I would put it there and in the readme.txt. Maybe add:
I'm not sure if you have to wait on setting your subdomains until after. If so, that should probably noted as well.
I think maybe others might not be so lost. Maybe its a newbie blunder. But, I was so lost. I read through the instructions over and over and just didn't see any particular issues in the sequence I was using. It wasn't until you suggested the error logs I figured it out. They led me to read the files in the Domain Conf folder and I realized the dependency of the domain_id. Without it being set there was nothing to reference, hence the loop.
Thanks for all your assistance. It really is a a great module. It beats the other options to build multiple sites off one database. There are so many companies with multiple brands that need one central area of control.
You rock, sir!!
Mystical
Comment #11
agentrickardChanging title
Comment #12
scedwar commentedJust a thought, maybe put a warning on the description on the module install page or prevent it from installing until Domain is at least installed?
More generally, the readme is very clear, but it does require following carefully which is unlikely to happen all the time!
It might help if the domain modules were grouped in the modules list into a 'Domain -core' group to install first (and get properly configured) and then a "Domain -optional" category with a warning to make sure the core modules are properly configured before enabling any of them (or prevented from installing at the same time as the "Domain-core").
Comment #13
agentrickardI like this second idea -- a little -- but it would clutter up the UI for the modules page.
The issue here wasn't with Domain module installation -- the modules code prevents that -- it was adding the including prior to the Drupal installation sequence. That is a no-no and is not documented.
Comment #14
agentrickardThis has been added to the main INSTALL.txt file.
Comment #15
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.