(Content editing forms:) *
(.)Take user to their assigned domain

I think an example may help to make this a complete explanation in the READ ME.txt
"Before being presented the editing form, users will be taken to the first domain assigned to their user account. This function is most useful when you users are only allowed to enter content from a single domain."

Eg. If a user is assigned to one.example.com when he clicks on content type under 'Create content'-->Story from another domain ,say two.example.com the user willl be spontaneously taken to content editing form at one.example.com/node/add/story instead of two.example.com/node/add/story.
An advantage of this option is the user assigned to one.example.com can not modify the URL of a content edit form shown to him (ie., one.example.com/node/add/story ) to match the URL of other domains ,say www.example.com/node/add/story and publish the content to that domain.

Please think of adding this to READ ME if its right

Also is there a handbook for domain access on Drupal...?

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

This is a great chance for you to learn how to write a patch ;-) http://drupal.org/patch/create.

nirvanajyothi’s picture

nirvanajyothi commented

thank you for the link.I dont know why you sent me this...To create patches and diggin deep into drupal would be a tough call for me.

BTW i have learned to apply a patch now...Congrats to me!

Also to add ...A user assigned to the primary domain can post content to any domain by modifying the URL of content editing forms.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Learning patches is a great step towards empowering yourself with Drupal. It will let you initiate feature reviews faster, since most developers like to review patches more than requests. You will also see great results because other users may download and test your patch.

If you can apply a patch from the command line, here's what you do.

1) Copy the README.txt to a new file README.new.txt in the same directory.
2) Make your edits to README.new.txt
3) Run the following command (or equivalent on your system):

diff -up README.txt README.new.txt > domain_user_README.patch

Then you should have a patch file in your directory that you can upload here. This is a very safe first patch, since it is only documentation, so you cannot break the module :-).

A user assigned to the primary domain can post content to any domain by modifying the URL of content editing forms.

Please open a different issue for that. This should not be true if 'Take user to their assigned domain' is checked.

nirvanajyothi’s picture

nirvanajyothi commented

"A user assigned to the primary domain can post content to any domain by modifying the URL of content editing forms."

Its true on my site. have posted as new issue here http://drupal.org/node/309350

thanks for teaching how to patch the Read me.will try it out tomorrow.bye .

-thank you

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Patch (to be ported)

Truncated to:

  The advantage of this option is the user cannot modify the URL of a 
  content edit form to match the URL of other domains, forcing all of her 
  posts to be made to a signled domain. Users trying to enter content 
  from another domain will always be transferred to their assigned domain.
  
  In effect, a user assigned to 'one.example.com' will only be able to post
  to that domain, even if she clicks Create Content from two.example.com.

And committed to HEAD.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Patch (to be ported) » Fixed

And to 5.x

nirvanajyothi’s picture

nirvanajyothi commented

a typo if its exactly gonna be in portposts to be made to a single domain

otherwise great!

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Fixed again.

Anonymous’s picture

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

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