Hi,
I have set up domain access module in my site. I used the domain user module and I want the user to be able to create their own subdomain and post their content only to their subdomain. But when the user tries to finish creating the new content, they will be redirected to example.com instead of username.example.com and they will encounter "access denied" page.
For example, if a user creates page with url content/new-item, after he finished submitting the form, he is redirected to example.com/content/new-item instead of username.example.com/content/new-item and hence he will encounter the "access denied" page. But actually the content page has been created successfully in username.example.com/content/new-item .
The same also happened when the user logs in for the first time and he wants to change the password. After changing the password, he is redirected to example.com too and encountered "access denied" while actually he has succeeded in changing the password.
my settings are:
New content setting: only show on selected sites
Content editing form: take user to their assigned domains
Domain based editing control: use access control for editors
For the authenticated user, they have the roles: edit domain nodes and view domain
I wonder if i missed something in setting up the domain access module?
Thank you for your help.
Regards,
Valent
Comments
Comment #1
agentrickardThese are two separate issues.
For node creation, see http://drupal.org/node/227947 for the full discussion. This is a "by design" behavior -- but one that we have been trying to fix.
For user login, that sounds like a configuration error. Please open a new issue for that and include:
a) The primary domain (an alias like example.com will do)
b) The domain from which a user is loggin in
c) The $cookie_domain you have set in settings.php
Comment #2
schturdark commentedHi,
For the node creation, I will try to read the link you provided and implement it. Will let you know the result. Thanks a lot!
Erm, I just opened the settings.php. It seems the root cause of user changing password issue was because I had not set up the cookie_domain parameter and it was still commented out too. I have set it up now and it solves the issue for the time being. Really sorry to take your time and cause you trouble.
Once again, thank you for your help!
Regards,
Valent
Comment #3
schturdark commentedHmm, I tried implementing the patch or suggested snippets but it seems that it is not working for drupal 6. Any chance to adjust the patch for drupal 6?
Thank you.
Regards,
Valent
Comment #4
agentrickardPlease comment in the other issue. This is a _duplicate_ which means it is not active.