Setvik,
firstly, thank you very much for a wonderful, useful and low-weight module. I have installed it on my site and find it working fine.
However, after installing subdomains, the existing subdomains I had working earlier disappeared. (There were separate installation of Mediawiki and dotProject, not related to drupal installation).
The setting is like this
Drupal site example.com is at /public_html/ (the subdomains in OG mode works fine and og1.example.com, og2.example.com work as they should).
There is a wiki site at /public_html/wiki/ which was earlier accessible by wiki.example.com
Similarly there was a dotProject site at /public_html/project/ accessible by project.example.com

I have made sure that I have specified these domains to be excluded by subdomains module (along with static and www).

But these original subdomains are now not accessible. Is there a way to rectify this?
-shas3n

Comments

setvik’s picture

setvik commented

It's difficult to know for certain without taking a look at it...

How do your mediawiki and dotproject subdomains break? When you try and access them in your browser, what exactly happens? are you taken to your Drupal website?

Are you on shared hosting? How did you configure your virtual hosts?

setvik’s picture

setvik commented
Status: Active » Postponed (maintainer needs more info)
shas3n’s picture

shas3n commented
Status: Postponed (maintainer needs more info) » Active

Yes, I land up on my drupal site when I try to access the wiki.
Yes, I am on a shared host. I dont have access to httpd.conf but I understand that the hosting provider has enabled wildcard subdomain.
Do you think I should try adding these subdomains as exceptions in httpd.conf or something?
Does subdomain module have any filtering where it does not try to hijack the subdomains if a folder by that name exists in /public_html/ ?
Is there any other kind of filtering that I can use to make the wiki subdomain work as expected?

These are not critical and if nothing works, I can settle for example.com/wiki rather than wiki.example.com But if would be nice to know if this is possible.

shas3n’s picture

shas3n commented
Status: Active » Fixed

I just deleted the subdomains and re-created them through cpanel and it solved the issue!!
I am not sure what changed.
Marking this as fixed. But feel free to add your comments if you have any insights into this.
Thanks!

setvik’s picture

setvik commented

The subdomain entry in CPanel is basically a user interface to the apache configuration file.

My guess is the wildcard subdomain directive was taking precedence over the manually configured individual subdomains you had setup in CPanel... it may have simply been higher in the configuration file. By recreating the subdomains in CPanel, they may have been pushed up above the wildcard subdomain directive, giving them precedence.

glad to hear it's working :-)

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.