I wud love to
1.
create a subdomain for all groups on my site (groups.mydomain.com) and all groups created to be created in the subdomain (groups.mydomain.com/'newgroupname') and
2.
allow users to access and post content to the groups they belong to with the same username n password as that of my main site (mydomain.com).And
3.
most importantly,all content posted in the groups set to 'public' need to be seen and accessed from the main site also.
Is subdomain the best module for achieving this?
(Am running a site on drupal 5.7)

Comments

setvik’s picture

Status: Active » Fixed

Sorry for the belated reply. Been gone a while.

1) Yep, subdomain allows you to do this
2) Yep, subdomain supports this (be sure to set $cookie_domain in settings.php)
3) Yes, subdomain supports this (create a view & have it display whatever group content you want to appear on the main site).

setvik’s picture

Status: Fixed » Closed (fixed)
setvik’s picture

Status: Closed (fixed) » Fixed
nirvanajyothi’s picture

thank you for the reply setvik.I really thought you had left the place when i didn get a reply for this long!

So is it right to say that its possible to share content of subdomains (created using the Subdomain module) with the main site.If so., how is it different frm Domain access module w.r.to sharing of content?

Can u explain few of the relevant differences b/w Subdomain and Domain accsess modules.Think it will help me and maybe many more users to choose b/w the 2 good modules to settle with the one that satisfies their needs.

nirvanajyothi’s picture

Status: Fixed » Active
setvik’s picture

The *only* thing the subdomain module does is rewrite URLs.
It extends pathauto by allowing you to automatically generate path aliases that incorporate subdomains.

I haven't used Domain Access, but reading the Domain Access module page, it appears to allow far more. If I understand it correctly, it basically allows you to create a bunch of affiliated Drupal sites on different subdomains, share content between them, and control user access to them.

It allows each subdomain to be an almost totally separate drupal site.

Here's a quote from their front page:

Included in the Domain package

  • Domain Configuration -- Allows you to change select system variables for each subdomain, such as offline status, footer message and default home page.
  • Domain Content -- Provides a content administration page for each subdomain, so that affiliate editors can administer content for their section of the site.
  • Domain Navigation -- Supplies a navigation block with three themes. Creates menu items for each subdomain, suitable for using as primary or secondary links.
  • Domain Prefix -- Provides a user interface for enabling select database table prefixing for use with subdomains. Not fully functional on pgSQL
  • Domain Source -- Allows editors to set a primary source domain when links are written to content from other domains.
  • Domain Strict -- Forces users to be members of domains in order to view content. This is a sample extension module that uses the API.
  • Domain Theme -- Allows separate themes for each subdomain.
  • Domain User -- Allows for the automatic creation of subdomains for registered users.
  • Domain Views by mrichar1 -- Provides Views integration through a filter and default argument.

Hope that helps a bit. When I have some more time, i'll test drive Domain so I can better explain the differences.

nirvanajyothi’s picture

Thanks a lot setvik.It really helped clear some of my doubts.
-Thank you

setvik’s picture

Status: Active » Fixed
richard.e.morton’s picture

I have a strange situation due ot the history of our site. Drupal has had to be put in a directory under root (/a/ - www.plusgroups.org.uk is html redirected to www.plusgroups.org.uk/a) for various political reasons it isn't possible to relocate it to the root.

Would this module also capture .plusgroups.org.uk and effectively redirect-it or return the page for plusgroups.org.uk/a/.

i.e. southampton.plusgroups.org.uk returns the page of plusgroups.org.uk/a/southampton

I am expecting a no cause of the way webservers wouldn't know that this request should go to drupal, but I thought I would ask.

Unfortunately we are on a shared host, so changing the apache httpd.conf isn't possible either

thanks for your help though - suggestions welcome!
R

Anonymous’s picture

Status: Fixed » Closed (fixed)

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