# Summary
What it does: The Domain Access project is a suite of modules that provide tools for running a group of affiliated sites from one Drupal installation and a single shared database. The module allows you to share users, content, and configurations across a group of sites such as:
- example.com, one.example.com, two.example.com
- thisexample.com <-- can use any domain string
- example.com:3000 <-- treats non-standard ports as unique
Why it is needed / common use cases:
- multilingual websites using the domain prefix language setting and needs distinct access by domain (e.g.: example.com, example.jp, example.co.uk)
(A sentence or two describing what this module does and why it's needed as well as a sentence on current porting status, if known.)
# Project URL
https://www.drupal.org/project/domain
# Where is the code?
https://github.com/agentrickard/domain
# Estimated completion date
Unknown by creator of this issue.
# Dependencies
(What other modules does this one depend on? Ideally, link to the dependent project issue if it already exists.)
# Who's doing the port?
Agent Rickard / Palantir
# What help do they need?
(Are there specific types of resources (e.g. skillsets, $, sprints) that would be helpful to expedite porting?)
Unknown by creator of this issue.
# D8 roadmap
#2313313: Domain Access D8 port
# Background and reference information
(Links to any other helpful information, documentation, etc.)
Unknown by creator of this issue.
Comments
Comment #2
Kazanir CreditAttribution: Kazanir commentedComment #3
ysaid CreditAttribution: ysaid as a volunteer commentedHello, when do you plan to release a stable D8 version ?
Thanks.
Comment #4
jonathanshawIntensive work ongoing in early December
Comment #5
agentrickardThe primary work is here -- https://github.com/agentrickard/domain
There is a detailed release checklist here -- https://github.com/agentrickard/domain/blob/8.x-1.x/CHANGELOG.md
Contributor onboarding here -- https://github.com/agentrickard/domain/blob/8.x-1.x/README.md
Open issues, tagged by Alpha, Beta, and Final release -- https://github.com/agentrickard/domain/issues
These are the Alpha release blockers:
https://github.com/agentrickard/domain/issues?q=is%3Aopen+is%3Aissue+mil...
Comment #6
drupalok CreditAttribution: drupalok commentedhello agentrickard
will the drupal 8 version be released any time soon?
i can live with bugs as long as there is an upgrade path...
we really need to get a drupal 6 site upgraded now...
thanks for your hard work!
Comment #8
DmytroKerest CreditAttribution: DmytroKerest as a volunteer commentedHello, I'm also interested in the module.
I can contribute under some guidance.
Comment #9
agentrickardIf you can help knock out the Alpha issues listed on GitHub, then the module can be considered stable.
I estimate about 160 hours left to finish the port, which would take me 3-4 months of weekends.
We haven't even worked on the migration path, however.
Comment #10
DmytroKerest CreditAttribution: DmytroKerest as a volunteer commentedI have busy schedule now, will get back here when have free time
Comment #11
finalred CreditAttribution: finalred commentedi'm waiting for domain theme,and thanks for your hard work!!
Comment #12
agentrickardAt this point, a module for Domain Theme seems unlikely. The UX work may be too burdensome.
However, it may *just work* if you use domain_config.
See https://github.com/agentrickard/domain/issues/102
Comment #13
finalred CreditAttribution: finalred commentedSee https://github.com/agentrickard/domain/issues/102
sorry,still don't know how to config the theme
Comment #14
Londova CreditAttribution: Londova commentedHi,
I am looking to use Domain Access for Commerce site.
Is it possible to include the Products, Stores, Taxonomies, Menu, etc. in the list for content control? Or for Commerce will be something different?
Comment #15
agentrickard@finalred
Theme settings are just configuration yml files now. So you can export a YML file, rename it 'domain.config.[DOMAIN_MACHINE_NAME].[CONFIG.NAME].yml' edit it, and then import to your site.
There is no UI for that, and we'd like to know what breaks when you try that. I would start with system.theme and create a file like so:
domain.config.example_com.system.theme.yml
Comment #16
agentrickard@British-Link
That's a complex, advanced use-case that I don't intend to support in the core module. Drupal core doesn't provide a native access control API for all entities, just for nodes.
The API in Domain is stable enough that you could use it to add the same domain fields to other entities, and then write the query alters necessary to enforce access control.
See https://github.com/agentrickard/domain/blob/8.x-1.x/domain_access/domain... and https://github.com/agentrickard/domain/tree/8.x-1.x/domain_access/tests/... for how to install the Domain Access fields on other entity types.
Comment #17
finalred CreditAttribution: finalred commented@agentrickard
Thanks! it works!
you are a big help to me
Comment #18
Londova CreditAttribution: Londova commentedWhile being logged in as admin, the Domain Access doesn't have any effect (content type - Basic Pages).
The content is displayed per domain only when logged out.
Are there settings which I missed and should pay attention to?
Comment #19
zerolab CreditAttribution: zerolab at Torchbox commented@British-Link you are likely checking as the site administrator, which by default bypasses this. Best to create a test user and check with it.
Also, worth noting that this issue is not really the place for support questions. Best to either open a new on on GitHub. Hopefully the 8.x alpha will make it to drupal.org soon, so usual issues can be created on d.o.
Comment #20
zerolab CreditAttribution: zerolab at Torchbox commentedThe first alpha is out.
Changing status to "Needs review" to reflect that.
Comment #21
Londova CreditAttribution: Londova commentedThe link provided is wrong.
Could you double check and correct it?
Thanks
Comment #22
zerolab CreditAttribution: zerolab at Torchbox commentedDone. https://www.drupal.org/project/domain/releases/8.x-1.0-alpha1 for posterity.
Comment #23
drupalok CreditAttribution: drupalok as a volunteer commentedthanks so much for your hard hard work and your alpha guys!
Comment #24
andypostWhere the main development happens? looks github has more activity
Comment #25
agentrickardGithub, though I sync back releases here.
Comment #26
iwsp CreditAttribution: iwsp as a volunteer commentedHello,
I want to change the theme for each domain, are there a usable version ? I have lot of Exceptions. Is it normal ?
Thank you.
Comment #27
geek-merlin@agentrickyard wrote in #16:
> Drupal core doesn't provide a native access control API for all entities, just for nodes.
I guess you already have an eye on that issue. If not:
See #777578-179: Add an entity query access API and deprecate hook_query_ENTITY_TYPE_access_alter() and the hopefully upcoming Entity Access Policies module. We surely want to keep an eye on that.
Comment #28
andypost@axel.rutz I'm following the issue but for integration for other entities you need
- https://www.drupal.org/project/domain_entity
- https://www.drupal.org/project/domain_language
And specific
- https://github.com/skilld-labs/domain_menu_access
- https://github.com/skilld-labs/domain_block_content
Comment #29
michaelswain CreditAttribution: michaelswain commentedI had three domains set up on a test server using the Domain Access module. I added three more, and also changed the hostnames in Domain Access settings for all six domains. If I log in as admin using the old hostname, I'm fine. If I use the new hostname and log in as admin, the login appears successful but I immediately run into a "Access denied - You are not authorized to access this page" message.
I checked every box in the Domain Access section of my user settings for the user admin (all affiliate domains, make this user an editor on all domains, make user an administrator on all domains). I rebuilt permissions. Still no luck. The only way I can avoid the Access Denied message is to browse to the URL of the original domain, before I added more domains and changed their names.
That's my specific issue, but more generally, can anyone comment on the status of this module's development for D8? Thank you.
Comment #30
ressa CreditAttribution: ressa at Ardea commentedI see that version 8.x-1.0-beta2 of Domain Access was released 24 June 2020, and it is great to see that the module is being developed, thanks!
Is the module ready for Drupal 8 and Drupal 9 production, and is it recommended to start considering an upgrade from a simple Drupal 7 Domain Access-based installation? I see that 4289 sites Drupal 8 sites use the module, so I am guessing yes, but the Beta-state is slightly disconcerting ...
Comment #31
agentrickardIt is beta only because it is not feature complete. We have test coverage for all current features for both Drupal 8 and Drupal 9.
The functionality and API are considered stable.
See #3101638: Stable release tasks for the list of remaining tasks.
Comment #32
ressa CreditAttribution: ressa at Ardea commentedThat sounds really good @agentrickard, I'll give it a test drive, and thanks again so much for working on it.