Hi,

Is it possible to have different

1) login page (be able to change the logo, site name ..., currently it will use base domain)
2) user dashboard (at least be able to customize differently, logo, site name ...)

for different domains? Currently the oa_domain makes it possible to have different domains for different spaces. Maybe we can add

Also, currently, if I am not a member in any access in any space in domain1.com. However I can login at domain1.com (since there is 1 public space in domain1.com and I have an account in the base domain domain2.com). This is not correct behavior according to the design in my opinion.

Should we add a field in user profile so that the user belong to one domain or their default domain?

hosais

Comments

mpotter’s picture

mpotter commented

Nope. oa_domains only affects Spaces in OA2. It cannot affect any other non-space page. There is no way to have different user dashboards per domain as there is only a single user record on the entire site.

The entire purpose of oa_domains is to have consistent user accounts across all domains/spaces, but just to change the URL structure within the spaces. If your needs are beyond that then you probably need to look into normal Drupal multisite functionality and set up separate Drupal databases on different domains.

hefox’s picture

hefox commented

Should this be marked as a support request and "fixed" (or marked as won't fix/works as design?)

hosais’s picture

hosais commented

Hi Mike,

Thank you for your clarification.

My use case is that the users are shared by different domains. oa_domains is a great way to do this. For example, a company has intranet but also use the same system to support clients. In this model, the good thing is that the content is very flexible and can change shared or not shared (to outside or another domain) easily.

The thing I would like is a little more clean environment different domain. The users can be only in one domain or both domains or another domain. Currently, oa_domains seems to be able to do only for sharing both domains or aware of both domain but only use one domain. Anyway. I understand the original idea is for a site can create space and have subdomain for users. According to your opinoin, it might be out of the scope of oa_domain; therefore, maybe domain access module could do this in this case. But I don know it is compatible with oa2 or not.

hosais

mpotter’s picture

mpotter commented

Domain Access is a tricky module (which is why we created oa_domains). So not sure how it would work. But it still doesn't solve the fundamental issue that there is only a single user dashboard in Panelizer. No way to make different dashboards for different domains unless you go into Panelizer and start creating different variants for each domain somehow (assuming Panelizer knows anything about the domain).

This is definitely something that would require a large amount of custom effort and definitely beyond the scope of the out-of-the-box OA2 distro.

hosais’s picture

hosais commented

Thanks Mike.

I still do not give up to user oa_domains since it seems a very cool option. I need more tests and time for clarify the use case. Thank you again.

hosais

Argus’s picture

Argus commented

I'm also interested in a solution for this, it would certainly have it's use cases. Perhaps it is possible when using Domain Access and it's submodule Domain Prefix, and then with Access Control Bridge to fix conflicts. Or perhaps someone one day will write some custom code.

#2: I tend to agree.

hosais’s picture

hosais commented

Hi,

I double checked with Panelizer. In theory, it cannot truly separate domains in oa2 but in practically, it is easy to do it (in the case of sharing all the users in one database), with some additional rules (such as roles are not the same or duplicated in the two domain or maybe some other rule policy), Panelizer can easily achieve this. As Mike mentioned: "assuming Panelizer knows anything about the domain".

Thank you for your help.

hosais

hosais’s picture

hosais commented
Status: Active » Closed (works as designed)
Argus’s picture

Argus commented
Status: Closed (works as designed) » Fixed

I was successfully able to separate users for each toplevel Space using the method described here: http://www.curveagency.com/blog/setting-drupal-multi-site-unique-user-ta..., in combination with oa_domains.

Argus’s picture

Argus commented

#9: Side effect with this method is that you will see a errors at the main domain (www.example.com) for each author that cannot be found for content belonging to a sub-domain; 

Notice: Undefined index: 8 in user_node_load() (line 3682 of /srv/bindings/13655b55951d4ae4a7e73623c1342111/code/modules/user/user.module).
Notice: Trying to get property of non-object in user_node_load() (line 3682 of /srv/bindings/13655b55951d4ae4a7e73623c1342111/code/modules/user/user.module).

You will see the author set to "Anonymous" at admin/content.This shouldn't be a problem as long as you do not intend to use the main domain, or at least don't intend to give users access to view all content.

Status: Fixed » Closed (fixed)

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