Hi, I've followed the instructions and patched the files. I had to manually patch the .htaccess file, although I think I've done it correctly. I got my host to enable wildcard although I haven't edited httpd.conf as I wasn't sure whether this was part of enabling wildcard, in which case my host should have done it (?). If not, where would I find this file?
I've followed along with the other instructions and would like to enable the subdomain module for users. The admin that was originally setup then aliased to:
site.com/adminadmin
After setup I created a test user, but the alias is:
~jboojboo
This is after having the automatic aliases set to [subdomain][user-raw]. Any idea where I might have gone wrong?
Thanks for any help.
Comments
Comment #1
Jboo commentedOk, I have this working!
It seems the settings.php file doesn't override in drupal 6 without CHMODing the whole folder, so the patched settings.php hadn't copied across. Should I also be patching the default.settings.php which is found in sites/default as well as settings.php?
I have placed [subdomain] in the user alias settings and it seems to be working great.
Thanks.
Comment #2
setvik commentedHi Jboo,
Nope, you only need to patch settings.php. You can leave default.settings.php untouched. It's unused by Drupal.
Glad you got it working :-).
Take care,
Stein
Comment #3
Jboo commentedThanks Stein, great module :-)
Comment #4
Jboo commentedHmm, I thought this was working, it seemed to be, but when going to where a users page should be I'm redirected to http://jboo.site.com/404.html. The links throughout the site link correctly to the subdomain for users but they are all then direct to 404. Is this a problem with the way I've setup the module or could my host have altered something? This is strange because it was working and I can't remember changing anything that might have affected the module!
Thanks for any help.
Comment #5
bflora commentedI am having a similar problem. Did you get this fixed? All of my subdomain links dump me to my front page instead of the group they're supposed to take me too. Incredibly frustrating.
Comment #6
broomy commentedNot yet, I'm trying to remember what I might have altered but I can't think of anything relating to the module.
Comment #7
setvik commented@jboo: sounds like Apache isn't rewriting your subdomain URLs correctly.
1 - Is Clean URLs enabled and working (that's a requirement i neglected to mention in the readme.txt)?
2 - have you updated pathauto's punctuation settings to allow ~'s in paths?
3 - Go through my reply in http://drupal.org/node/287951 and see if that helps.
Let me know how it goes.
Comment #8
setvik commentedComment #9
Jboo commentedThanks for the reply setvik. In response to your questions:
1 - yes, clean urls seem to be working fine
2 - the tilde option under punctuation settings reads "No action (do not replace)"
3 - my htaccess was slightly different on one line. I've changed to your suggestion in the post so the changes are:
Before:
RewriteRule ^(.*)$ index.php?q=~%1/$1 [L,QSA]After:
RewriteRule ^(.*)$ index.php?q=~%1/$1 [L]I'm on a shared host. I tried backing up my index.php for the test but the subdomain still doesn't work as I was just directed to a 404 page. The thing is it looks like it's working in terms of the redirect to subdomain.site.com on internal links of my site, and also once logging in as a user I get directed to subdomain.site.com, so that seems ok. BUT, whenever that page is reached it immediately goes to subdomain.site.com/404.html.
I had this working once so I can't see what I've altered that might have affected this module. I'll also contact my host to see if their have been any changes.
Thanks again for your support.
Comment #10
Jboo commentedOk, the problem was with my host! I contacted them and the response was:
"For some reason after the migration to php5/mysql5 it looks as if the * subdomain was removed from the apache configuration"
Thanks for pointing out the possible error setvik, I appreciate the support; great module.
Thanks
Comment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.