Port request for Domain Access

[stpaultim]

Name of the module, theme, or layout Domain Access

Link to the drupal.org module, theme, or layout https://www.drupal.org/project/domain

(Optional) Link to an issue in the drupal.org queue asking the Drupal community if anyone is working on a Backdrop port of this project https://www.drupal.org/project/forum_access/issues/3070491

(Optional) Bounty https://github.com/backdrop-ops/contrib/issues/400#issuecomment-738575348

Other This seems like it could be a pretty big project. I post the request, because I've had a couple of people ask about this module. It's come up in the forum at least three times and today it came up in Gitter chat.

https://forum.backdropcms.org/forum/does-backdrop-have-some-functionality-similar-domain-access-module

https://forum.backdropcms.org/forum/domain-access-equivalent

https://forum.backdropcms.org/forum/multiple-domains-pointing-same-site-how

Maybe there could be a light weight version for Backdrop CMS?

[yorkshire-pudding]

@izmeez - Wikis are better for longer documentation and are also easier for more people to add to. READMEs for Backdrop are expected to be quite short.

[izmeez]

@yorkshire-pudding Thanks, that's what I've observed. Since the namespace for the wiki is already established it really is just copy and paste from the recently modified files for Backdrop.

[izmeez]

I've started work on the wiki. I'd like to see the Home page deleted as I have replaced it with 1. Domain module wiki. I have also added 2. Domain Quick Start with more cleanup and more is still needed.

[izmeez]

@rudy880719 and @sudipto68 have identified that the problem is the syntax used for defining the $database. See https://github.com/rudy880719/domain/issues/4 It fails if the sort syntax is used $database = 'mysql://user:pass@localhost/database_name';

Using the extended syntax like D7 works:

$databases['default']['default'] = array(
  'driver' => 'mysql',
  'database' => 'database_name',
  'username' => 'user',
  'password' => 'pass',
  'host' => 'localhost',
  'port' => '',
  'charset' => 'utf8mb4',
  'collation' => 'utf8mb4_unicode_ci',
);

[rudy880719]

@izmeez something important for everyone, remember to rebuild permissions after installing the module, another thing to keep in mind is that if you have caches for anonymous users activated, every time you edit content and define something new related to the domain, you will have to clear cache to see the changes. To test, it is advisable to deactivate the page cache.

[izmeez]

It is odd that one method of declaring the database works and the other does not.

[izmeez]

The rebuild permissions option should be more accessible on the domain configuration pages. I found it on the Status Report and added that to the notes.

[izmeez]

@rudy880719 What do you think about combining both ports in the same repo as different branches?

[rudy880719]

@izmeez Sure, I agree, I'll delete the drupal branch and then we can take it to the other repository.

[izmeez]

I don't know what is the best way, you want to prune the branch from the point where it branched from D7 and move that branch to the other repo.

[yorkshire-pudding]

@izmeez @rudy880719 @sudipto68 - Thanks the db tip works. We can look at addressing that as we tidy up. I'm investigating the best way to add this branch to the repo.

[rudy880719]

@yorkshire-pudding Could you help me create that branch in the backdrop/domain repository, I need to know if I should delete the drupal 7 branch from my repository.

[yorkshire-pudding]

@rudy880719 - yes - I've just been getting some advice on how to do this. You don't need to delete the D7

[LittleDuke]

My firm sphi.io would be willing to donate to this project. @stpaultim knows us. we are wholly dependent on this module in D7

[stpaultim]

@LittleDuke - Your timing is good. There is some active work being done on this module now as you can see. Maybe your offer of help could help put this across the finish line.

[LittleDuke]

Thanks @stpaultim for your support! We cannot migrate to BD without this and would be a huge advocate for the project both publicly and potentially financially. As it is now we're actively working on replacing our entire front-end user experience with WP plugins dialing home via API. You know how to get ahold me...