I must be overlooking something as I can not seem to get the links on my primary domain to redirect to the content on the sub domain as dictated by the multi domain module settings.
When on the www.mydomain.com site, I create a story (e.g. "my drupal story") and then I select a sub domain (subdomain1.mydomain.com) under the domain category selector on the content submission forum.
The story is created as /my-drupal-story off of the primary domain and on the subdomain......so it can be reached as subdomain1.mydomain.com/my-drupal-story and at www.mydomain.com/my-drupal-story
What I want to be able to do is when a user is on www.mydomain.com and clicks on "my drupal story" it brings them to the subdomain version and not to the version on the primary domain (which is happening now.)
I basically want my taxonomy categories to be sub domains linked from a primary domain landing page and was hoping that this could be achieved with this module.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | multidomain-alias.patch | 760 bytes | nedjo |
Comments
Comment #1
bacchus101 commentedA clean re-install fixed the issue. Not sure what was causing the url's to not properly rewrite but I am moving on ;)
Comment #2
bacchus101 commentedI actually found the problem as I walked right back into it and now am in the same situation as initially posted.
If I use pathauto or specify a custom URL using the path module it creates two copies of the story -- one on the subdomain (category) specified and one on the primary domain. The copy on the primary domain front page points to itself (mydomain.com/my-drupal-story) and the one on the subdomain points to itself (subdomain1.mydomain.com/my-drupal-story)
If I turn pathauto off and do not suggest a custom url it will write as subdomain1.mydomain.com/node/X and when I click on the story from the primary domain it will direct me to the proper place on the subdomain.
Is there anyway to get clean user (auto) generated paths (for SEO consideration) AND have the Multiple Domain module rewrite capability?
Comment #3
nedjoThe issue is a bug in the code used to determine the current path for taxonomy and node type matching.
When matching the path arguments, we need to use the real path, not a potential alias.
Patch attached.
Comment #4
MentalFS commentedIs this one now fixed? I'm going to use pathauto and multiple domains, but I'm not sure if it will work.
Comment #5
Duncan Pierce commentednedjo's patch works for me.
Comment #6
wayland76 commentedLooks good, seems to work for others. I'm changing it to "ready to be committed".
Comment #7
summit commentedHi,
Thank you for this great module! I revived it on a site and subsites of mine and it is working great.
Subscribing, wil this patch be committed soon? Greetings, Martijn
Comment #8
wayland76 commentedThis module no longer appears to be supported. I recommend http://drupal.org/project/domain as an alternative.
Comment #9
summit commentedHi,
For my purposes, this module is enough and just what I want for a certain site.
For other purposes I will change to domain. Please do'nt let die this great module also, because I think they both have a live!
Multidomain for simple having the same content on different sites, Domain for all other purposes of domain-sharing!
Greetings,
Martijn
Comment #10
wayland76 commentedWell, Martijn, I don't know of anyone else who is interested in keeping it going. I admit, though, I've nicked parts of it and used them as patches to the Domain module.
If you want this module to keep going, you'll need to do it yourself, because AFAICT the original developer disappeared some time ago, although there have been a few other contributors.
Comment #11
sunhmmm... nedjo? adrian? Is #10 true? If so, I'd be open to take over this module.
Comment #12
summit commentedHi Sun, great! Greetings, Martijn
Comment #13
sunI hereby revoke my offer. Instead we'll integrate multidomain's features into the Domain Access module.
Comment #14
summit commentedHi Sun, Also great! then I can use one module for both situations, great! greetings, Martijn
Comment #15
betz commentedPatch committed to the development snapshot.