I managed to install subdomain successfully. But I am not able to implement this feature on my site. I have few content categories which I want to behave as subdomain.
For example for the category "business" which is currently located at http://example.com/category/categories/business, it should get redirected to business.example.com. Things to be noted are: category is the path that I put myself in the pathauto module and categories is the vocabulary that I created. Business is the entity in the categories vocabulary.
To create the subdomain this style I did the following:
(1) Installed the subdomain module for my site which is on linux dedicated server and ensure everything is working required by it. In URL aliases --> subdomain settings I can see all the five requirements working correctly.
(2) On the same page I selected Create subdomains for "taxonomy vocabulary and associated content" and also ensured that With the selected vocabulary terms "Categories" as this is the vocabulary that I want to target to.
(3) Saved the settings and moved on to URL Alias --> Automated Alias settings and put the [subdomain] for the Pattern for all Categories Paths under Taxonomy path settings such as [subdomain]/category/[vocab-raw]/[catpath-raw]. Saved the settings and tried to access the category as sub domain but could not succeed.
Another thing to mention is that I did not create a sub domain "business.example.com" through cpanel yet as I thought it might work without it. Please help regarding all this.
Comments
Comment #1
nikmahajan commentedstill waiting for an assistance.
Comment #2
nikmahajan commentedno one to help?????????????????? Module developers should help at least.
Comment #3
pyallen97 commentedI feel you're pain nik. Getting people to answer forum posts here is like pulling teeth. It seems to happen randomly.
As to your issue, I just unistalled 6.x.2.0 and am giving 6.x-1.7 a shot (6.x.2.0 is a total nightmare to use). As I am just starting with 6.x-1.7, give me a day or so. If i get it figured I'll let you know.
Comment #4
colemanw commentedPlease see #844170: New documentation ready for posting