Jump to:
| Project: | Subdomain |
| Version: | 6.x-1.7 |
| Component: | Documentation |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Issue Summary
Given the large number of issues in the queue relating to people not understanding what this module does and how it works, I have rewritten the description for the front page. This should clear up a great deal of confusion and cut down on the number of support requests being posted. Here it is:
OVERVIEW:
Subdomain extends the functionality of the path and pathauto modules to allow subdomains as part of a url alias.PATH EXAMPLES:
Giving a node the alias "~blog/2010/it-works" would result in "http://blog.mysite.org/2010/it-works"
To create a subdomain's "homepage," simply give a node, view, taxonomy page, etc an alias like "~blog" and it will resolve to "http://blog.mysite.org"PATHAUTO EXAMPLES:
Place every node of a certain type on a subdomain by giving it a pathauto setting like "~blog/[field_date-yyyy]/[title-raw]"
Use a CCK field to set the subdomain with a pathauto setting like "~[field_custom-subdomain]/[title-raw]"SUBDOMAIN TOKEN EXAMPLES:
The Subdomain module is also capable of generating 4 special tokens, based on node author, content type, taxonomy, or organic groups. To use this feature, chose one of those four options, and the token [subdomain] will become available. Place it at the beginning of a pathauto setting like "[subdomain]/[title-raw]" to produce results such as:Node Author:
EXAMPLE: A user named "Mary" and her nodes would be at http://mary.example.comNode Content Type:
EXAMPLE: Nodes with a content type of "News" would have URLs like http://news.example.com/drupal-is-the-greatest-web-tool-everTaxonomy Vocabulary:
EXAMPLE: A term named "Seattle" and associated nodes would be at http://seattle.example.comOrganic Group:
EXAMPLE: A group named "Pizza Lovers" and its nodes would be at http://pizza-lovers.example.comDEPENDENCIES:
PathautoINSTALLATION:
Please see the included README.TXT file for detailed instructions on how to install this module.NOTE: subdomain requires changes to your DNS server and web server. See readme.txt.
Sites using subdomain:
http://eslwell.comEnjoy!
RELATED MODULES:
Domain Access: If you wish to share content across multiple domains, you might want to try the Domain Access module. Domain Access provides advanced tools for running a group of affiliated sites from one Drupal installation and a single shared database. It differs greatly from the Subdomain module in its approach and use-cases, consult both modules' documentation if you are unsure which to use.
Comments
#1
please review
#2
Thanks for writing up some new docs and sorry for not seeing this sooner!!!
I'm in the process of simplifying the subdomain module (6.x-2.x) so that it doesn't rely on pathauto or url rewriting.
The 2.x version is much much simpler to install and configure, so when it's in beta (hopefully in a few days), i'll make it the recommended version and deprecate 1.7 (remove it from the list of supported versions).
I could really use some help testing the upgrade process from 1.7 to 2.x (backup your database first). Once I've gotten confirmation from a few people that the upgrade is working alright, i'll move it to beta.
re: the documentation. As the 2.x version doesn't involve url aliases or pathauto and I'm encouraging new users to install the 2.x version, it may be good to split up the front page documentation according to module version (i.e. putting the bits about path, pathauto, and tokens under the 1.7 version).
I'll try and update that later today or tomorrow.
Thanks again!
#3
I'm sorry, but I fail to see how the new version is an improvement. Almost all of the functionality of the 1.x branch has been removed. Please correct me if I'm wrong, but it seems that the new version of subdomain does not allow:
-a node to be specified as a subdomain's "homepage"
-a view to be placed on a subdomain (other than as the homepage)
-a non-node (such as a taxonomy page, or a page defined in "hook_menu" by a custom module) to be placed on a subdomain
-content to be placed on any arbitrary subdomain (in 1.x this is done simply by starting your path alias with a "~")
All of these things were possible (and very useful) in the 1.x versions. Take a look at the documentation I posted above for a complete list of everything it could do.
#4
How do you set the front page if you are using 6.x-2.0 release? I haven't found this in the documentation anywhere.
#5
To set the front page of a subdomain, use 6.x1.7 and see instructions above. The 2.x branch provides almost no support for this.
#6
How do I get a user who knows nothing about tokens or aliases to create their own subdomain with their own stuff on their own? The average user has no idea what I'm talking when I explain this and doesn't want to hear it. To be honest, it took me a while to figure out how to do this on my own and I've used Drupal for a little bit.
It seems to me that 6.x.2.0 and 6.x.1.7 are two separate parts of what could be a decent module. 6.x.2 at least gives users in their own account a very explicit, direct, simple way to create their personal sudomain. The problem is that 6.x.2 made it impossible for the user to get their content on their sub, which 6.x.1.7 does very well. Can you two work together and combine both versions so that this module becomes a real asset and not a pain in the ass?
#7
@ pyallen97
I can't quite tell what you mean by "create their own subdomain on their own." Do you mean you just want all nodes authored by them to be on a subdomain with a name you assign? Or a name of their choosing? Or ________?
If it's the former, you can quite easily do this with 1.7 simply by placing the appropriate token in the pathauto settings of your user-created content type(s).
If it's the second option, I would opt for a custom user profile field ("name your personal subdomain"), then use rules to create the path aliases based on that field. Again, no problem with 1.7, completely impossible with 2.0.
If it's the _______ option you're going to have to be more specific about what you're trying to accomplish. But in my experience there's really nothing that subdomain 1.x can't do.
#8
This is life saver documentation. Thanks
#9
Ya, I'm really debating switching back to 1.7 since I lost a ton of functionality that I needed. This new version seems like it's incomplete.
I need to be able to set individual subdomains, like ~user/john-doe > user.example.com/john-doe.
It's my understanding that in 2.x I can only set the "special token" on a specific category and from that point on, it's automatic. No individual control. I don't like it. I want the freedom back.
#10
@colemanw
I think you got it with the second option. Basically I was looking to allow users the ability to create what amounts to their own page with their own content. That page should be accessible via a subdomain: johnsmith.example.com. I'm hoping to keep the creation of that subdomain as simple as possible for users. So I think the custom field you suggested would work. I just have to figure out how to make that actually work. I think it's do-able though. Thanks for the help.
Just to be clear, though, 2.0 will never allow this functionality? Will I be missing out on anything important by not upgrading? Any security features? Thanks again.
#11
I honestly have no idea what's going on with the 2.x branch of this module, and the developer has failed to participate in these discussions so we can only guess.
Personally I think neither version of this module should be used for anything other than hobby sites, since they are incompatible with rather important modules like boost and securepages, break all kinds of ajax requests and generally take a pretty "non-recommended" approach to the multisite thing (the recommended way is to do a real multisite Drupal install).
#12
I have tried to install this module for 2 days.. and after trying the 2nd branch (major failure) and the 1.7 I still couldnt get it to work.. finally I tried version 1.6 and was able to get it to work. This module has huge potential but the creator really needs to simplify the branches and make them more stable and consistent.
Hopefully this helps somebody else.
Just my 2 c's.
Cheers.