The module is great and it has a lot of features and capabilities. And it suites my needs.

I spent much time searching the issues (some are relevant, but didn't help) and I read the Readme file several times and I can't get it to work.

What I would like is that when a user is registering to a subdomain, he will belong only to it. And when that user creates a node in it, the node will be shown only for that subdomain.

Currently registered users belong to localhost (the primary domain) instead of the registered subdomain, and nodes can be viewed by other subdomains(and if they are not published to localhost , they can't be viewed by the source subdomain itself)

I would very much appreciate it, if you could specify the required settings for it to work like this.

Maybe its because the Drupal installation is located in a sub folder (ilh). In the domain list page, the domain column is in this pattern: example.com/ilh

Thanks a lot for the help.

Comments

agentrickard’s picture

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

This is not an issue with subfolders of your installation.

Users are assigned to the domain from which their account is created. If they registered from localhost, they may be assigned to both that domain and to their personal domain -- check their accounts to see if this is the case.

Additionally, note that content is automatically assigned to the domain from which it was created. So if the user is posting to localhost, that is where the content is assigned. You can use the 'view domain publishing' permission to alter this behavior and force the user to go to their assigned domain.

Also note that all new content may be assigned to 'all affiliates' if that configuration option is selected.

Ehud’s picture

Ehud commented

Thank you for your reply!

New users are always assigned to localhost, no matter to which domain they register. Is there something spacial to configure for this separation to work?

'view domain publishing' permission is already granted. I also selected 'Take user to their assigned domain' in the 'Content editing forms section', and 'Only show on selected sites' is selected in the 'New content settings' section.

But new content from specific domain (not localhost) is shown in all domains. And if i change domain access for the user, to only that domain, I get 'Page not found', when I try to add content.

Other configuration I changed is in the 'node settings' menu. I cleared the mark for the node types that i am working with.

agentrickard’s picture

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

You have several different issues here, and it is hard to follow the exact problem. For instance:

"But new content from specific domain (not localhost) is shown in all domains." -- this is true if you are looking at the site as user 1 or as a user with 'administer nodes', since Node Access rules do not apply.

If new users are assigned to localhost no matter where they register from, then that is a bug,

Ehud’s picture

Ehud commented

I'll try to explain it better..

I am looking at the site as a regular user (authenticated), not user 1 and with no 'administer nodes' permission.

Users are assigned to localhost no matter where they register from... This behavior is since I installed the module.

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented

Can you answer these questions please:
1. In Domain module behaviors (admin/build/domain), what is "New content settings" set to?
2. In Node settings (admin/build/domain/advanced) in "domain node types" section, are the node types checked?
3. Did you install rc6 or did you upgrade to it?
4. Do you have any other modules altering user's default domain settings installed (Domain User Default) for example?

1-2 should answer why the nodes show up on all domains and 3-4 might explain user defaults.

Ehud’s picture

Ehud commented

Here are my answers:

1. 'Only show on selected sites'
2. No. the 'page not found' message now appears only when the owner user (not admin, but with permission) tries to edit the node. This behavior is not stable.
3. I installed the rc6 version directly.
4. No.

Thanks!

Ehud’s picture

Ehud commented

I didn't mention that I'm using the multiple_node_access patch. I saw in one of the issues that it is needed. But the problems occured even before the patch install.

I'm pacing now another issue, with the domain theme module. I get 'Page not found' when I try to access the theme page from the domain list (/admin/build/domain/theme/2 for example).

I get the feeling that maybe something basic is wrong here in this case.

agentrickard’s picture

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

Please don't confuse issues. The theming issue is not relevant here, and I answered it somewhere else.

What other node access module are you using -- THAT is very relevant.

Ehud’s picture

Ehud commented

I'm not sure which is a node access module, but these are installed and might be related:
Path, Devel (and devel node access - installed only after this issue begun), Location, Pathauto, Quick Tabs, album photos.

They are probably not related, but I mentioned them just in case..

Thanks

agentrickard’s picture

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

None of those are node_access modules. Why did you install the multiple node access patch?

agentrickard’s picture

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

Wait, let me back up to the most obvious:

You said In the domain list page, the domain column is in this pattern: example.com/ilh. This is wrong.

When you entered your domains, did you include paths? Don't. They are not needed and may cause errors (like these!).

Just enter example.com

This is noted in the form field description. The module is smart enough to determine the subfolders.

Ehud’s picture

Ehud commented

I tried to remove the path from the domain in the domain list page(so now its example.com). When I do it, and try to go to http://example.com, i get another local site from an old installation that is located in the root (directly under htdocs folder).

Should I move this installation to a subfolder too?

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented

I'd recommend sorting out your local Drupal installs. One hostname cannot be used for two installs at the same time.

drupal3008’s picture

drupal3008 commented

I'm having the same issues. I do not want my subdomains to share users. So when I'm creating new users (let's say from abc.example.com, it is automatically just assigning them to www.example.com, and not abc.example.com), it isn't creating and assigning them to their own domain they originated from.

Ehud’s picture

Ehud commented

Sorry, that didn't help.

New subdomain users still appear in localhost instead of the subdomain (-in the user domain access settings).

And the new subdomain user cannot add content. He gets 'access denied' message.
Here are my main settings again:

New content settings: Only show on selected sites
Content editing forms: Take user to their assigned domain

Node settings/Domain node types - cleared checkbox from types I work with

User defaults - didn't change

domain module permissions granted for authenticated user: 'edit domain nodes' and 'view domain publishing'.

Thanks again for the help here.

agentrickard’s picture

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

@Ehud

I think you need to start over and read the documentation. You seem to be fundamentally misreading how subfolders work.

When you browse to a site, you still need to go to example.com/subfolder. When you _register_ a domain with DA, you do not need to include the subfolder. DA is smart enough to figure it out.

You also need to make sure that all your domain DNS (or host) records are pointing to the same Drupal installation. For example, I run a testing server on MAMP, installed in the folder:

/Applications/MAMP/htdocs/drupal-6.10

My localhost Apache hosts file looks like so:

127.0.0.1	localhost
127.0.0.1 example.com
127.0.0.1 one.example.com
127.0.0.1 two.example.com
127.0.0.1 three.example.com
127.0.0.1 ken.example.com

And I have DocumentRoot (in httpd.conf) set to /Applications/MAMP/htdocs>/code>.

I browse to different domains at http://ken.example.com/drupal-6.10. These are registered with DA with the exact pattern that exists in my hosts file (e.g. ken.example.com).

The be sure that you only have one settings.php file. You should probably also check your $cookie_domain setting.

I think all your issues are related to server misconfiguration.

@makingbigthings

I don't think you are having the same issue, based on your comments in #302945: Don't need single/common sign on. Ehud is not using Doamin Prefix.

Ehud’s picture

Ehud commented

Thanks. I figured that already.

I will look into the other issues and hope I'll find something.

Ehud’s picture

Ehud commented

Sorry for the delay.

I checked the issues above and didn't manage to find anything wrong. And everything else works.

I have 2 other installations for other projects, and they are ok. No server issues that can indicate any misconfiguration.

agentrickard’s picture

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

See #443836: Users gets assigned to default domain, not current

Ehud’s picture

Ehud commented
Status: Active » Fixed

Thanks a lot !!!

It solved my problems!! users and nodes are now assigned to the domain from which they were created.

agentrickard’s picture

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

Sorry. That was a bad bug.

Status: Fixed » Closed (fixed)

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