i spent MANY hours trying to get this set up. yes i have shared hosting, but competent hosting, who would set *.example.com up properly, when i went to foo.example.com, 404 but taxterm.example.com (After setting up tax terms) redirected to output of category nodes. but trying to browse to a url like "taxterm.example.com/some-title-here" gave me a continual redirect loop,
i traced through the code, all was fine, so couldn't figure out why it was happening - totally gone crazy, then through desperation i just happened to read through an old support request:
as soon as i turned global_redirect off, the redirect stopped, and all is fine now :)
i guess this module makes global redirect redundant anyway, so, could it be put in the documentation about the incompatibility with the module and how you should disable it if you don't want to go mad ;)
thanks for a great mod
Comments
Comment #1
setvik commentedGreat idea.
I'll add it to the front-page description and readme.txt file.
Comment #2
George2 commentedtechnically, "Global Redirect: Using globalredirect at the same time will result in eternal redirect loops when you attempt to access a subdomain." is incorrect. foo.example.com will work if = 404, foo.example.com/fooboomoo will work if a 404. however, accessing a real node on a subdomain will cause the loop :)
Comment #3
setvik commentedTo clarify, do you mean that foo.example.com results in a 404, while e.g. foo.example.com/some-node results in an eternal redirect?
Comment #4
George2 commentedwell, if you just do anything.example.com = 404
though, if you set up, say subdomain on a vocab, then taxterm.example.com will give a list of nodes for that tax term, so will work as expected
however, taxterm.example.com/title-of-node = eternal redirect
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.