Module Multisite

[VeenarM]

I've just managed to set this up, and whilst it took a while it can be done.

Again - took for ever to realise that the domain needed to be in the config->httpHosts file.

Then you realise your sitemaps are all broken because the title with the domain doesn't have a url, it points to itself. So I played around with multilevel subdomains etc, and it all works kinda well now - http://dayswithoutincident.net/site-map/

the sub domain verison just implements the site-map template at the moment, but i needed to change the  templates and the php include files in order to achieve this.

[bernhard]

your url for the site dota2.dayswithoutincident.net in your sitemap links to http://dayswithoutincident.net/dota2.dayswithoutincident.net and then redirects to dota2.dayswithoutincident.net

not sure if thats by intention?

[VeenarM]

Yes that's the intended for the moment. The Module does the auto-redirect, I can't figure out how to send it to the other subdomain at the moment with out doing string manipulations.

At the moment its kind of like  if $page-> url ="/" && $page->id != 0 and its title is in the host file, then etc... to fix the directs.

If I can solve the other part then I'll look into it, but for now it's actually working really well

Cheers

John

[thomas]

Hello everyone,

I'm having the same problem. Funny thing is, it worked until I left for a week. Came back, no more luck ...

The subdomain homepage works //sub.domain.de/

Every child page //sub.domain.de/page/ gets redirected to //sub.domain.de/

Then I get 

Notice: Undefined index: it in /site/modules/Multisite/Multisite.module on line 68

Accessing //domain.de/sub.domain.de/page works fine

I tried debugging it using error_log at a lot of places but can't figure it out. Apeisas original module does the same but without the notice. Something tells me it could be a server configuration issue since all I did was update Apache. Everything works fine though so I can't see a reason why this won't work.

Has anyone found a solution? I'm halfway in my project and need multisite for this to work!

Thanks,

thomas

[heldercervantes]

This isn't working for me.

I have added the domain to the module and the page on the site root with exactly the same domain. Testing always leads to the main homepage.

Accessing firstsite.com/secondsite.com is leading to the root as it's supposed to. With the module uninstalled, firstsite.com and firstsite.com/secondsite.com turn out different pages as expected. But with the module installed, they all deliver the homepage.

I'm running PW 2.6.8

[heldercervantes]

Well I got it working, thanks to VeenarM's post. I needed to add the second domain to config->httpHosts.

How can I set this up via API?

I mean my site lets users register and gives them a private page. I want to automatically set thing up so they can just point their domain to my server and get a webstie.

[OrganizedFellow]

I find this to be an incredibly useful module!

I wish it worked as intended  

[cstevensjr]

I find this to be an incredibly useful module!

I wish it worked as intended

If you are actually having a problem, could you please be more specific and detail what your issues are?  Thanks.

[OrganizedFellow]

If you are actually having a problem, could you please be more specific and detail what your issues are?  Thanks.

I've got a large project coming up and went with Option #1 [https://processwire.com/api/modules/multi-site-support/]

Mostly because I need the organization (I AM an organized fellow).

When I tried Option #2, I just encountered a bit of complexity, that's all really. Option #1 was fairly quick and simple to implement.

I wish it worked as intended 

I was a little confused for a while. Didn't know if I had to edit my /etc/hosts file or my vhosts to "point" to the main domain.

Then after I got it all worked out and it went smoothly, I was not able to access a URL without the trailing slash:

mainsite.dev/ -> worked fine  

mainsite.dev/testpage1/ -> worked fine

test.mainsite.dev/ -> worked fine  

test.mainsite.dev/testpage2/ -> worked fine

test.mainsite.dev/testpage2 -> threw a 404 error, page not found, without the trailing slash

 

I did all my testing on localhost, Debian Jessie 8.2. I doubt it was a server config. My Digital Ocean droplet is nearly identical to my home setup, so I am certain I would have had issues there as well. I just did not deploy to verify 100%.

 

So, I just went back to Option #1 after reading all these 8 pages and testing out every option and code snippet offered. But no worries though  

[Tom Moe]

Hello all.
In the past I've made a lot with TYPO3, but now I've done my first project with PW, and it works well. Now I have a new project with a multidomain site which I want to
realize with PW. So I installed the multisite module from https://github.com/apeisa/Multisite/blob/master/Multisite.module.

And now I have a problem with this.

There are 5 Domains.

- MainDomain.de (with webspace/php/mysql on Server A)
- MyDomain2.de (only Domain hosted on Server B)
- MyDomain3.de (only Domain hosted on Server B)
- MyDomain4.de (only Domain hosted on Server B)
- MyDomain5.de (only Domain hosted on Server B)

MainDomain is the standard PW Site and full functionally on my DevServer. I've created the MyDomains under the homepage and made them hidden and made the entrys in the module settings. There is also an entry for each Domain in config.php.

On Server B I've made redirects for the domains to http://MainDomain.de/MyDomain2.de, http://MainDomain.de/MyDomain3.de

and so on and I hope I've done it right.

When I'm logged in into PW and open MyDomain2.de the browser shows MainDoman.de/MyDomain2.de and I can see the content of MyDomain2.de

When I'm not logged in into PW and open MyDomain2.de I get a redirection error and nothing shows up. Maybe I'm a little bit stupid but I can't locate my error for hours.

Maybe someone is able to help me.

[bernhard]

Hi tom moe and welcome to the world of processwire

You have to set your A records of all domains to the server IP of the server that is running the multisite installation of processwire (server a in your case)

A redirect won't work! Good luck

[bernhard]

me once again

Notice: Undefined index: it in /var/www/html/site/modules/Multisite.module on line 68

https://github.com/somatonic/Multisite/blob/master/Multisite.module#L68

i got this error today when i switched debug mode "on". PW 2.6.2

what is the "it" get parameter or what does it stand for?

changing this

$new_it = $_GET['it']; // we store it to later append it back

to that

$new_it = $this->it; // we store it to later append it back

solved the problem. the undefined index warning only appears on "root" pages when no further urlsegments are defined.

$this->it is set on line 45:

$this->it = (isset($_GET['it'])) ? ltrim($_GET['it'], '/') : '';

@soma:

any news on a new version? i think you mentioned it somewhere?!

[Soma]

Sorry for not replying. I was too busy, not only with updating this module.

There's now a new dev version that fixes issues and improves some things. 

https://github.com/somatonic/Multisite/tree/dev

For example the biggest change is that the configuration is now set in the config.php via an array in $config->MultisiteDomains

$config->MultisiteDomains = array(
    "dev.domain.com" => array( // domain name can be used to map to root page
            "root" => "www.domain.com", // page name for the root page
            "http404" => 27
        ),
    "dev.domain2.com" => array(
            "root" => "www.domain2.com",
            "http404" => 5332
        ),
);

This allows for different domain configurations on a dev and live stage, and since it's not in DB (via the module config) it can be easily transfered with a dump without worrying to overwrite or change the settings.

Also there's no need to change the domain "root" pages name, as it's not directly coupled to the requesting domain. So you only change the array keys (=domain).

Since the whole concept is all a pretty hack, I found that it comes with some complications that can't be solved in a elegant way. So for example the biggest issue is that you can't crosslink pages via the RTE Link plugin, since it doesn't know about Muiltisite. So you'll end with wrong URL's when for example link from a page of one site to a page of another site. If that's an issue it's still possible to copy the ProcessPageEditLink.module and modify the root parent for the page tree select. I'd be glad to help out with an example there.

Further, the structure of a multisite install needs to be

- Web (PW root page, I call it always "Web" since it isn't the homepage anymore)
   - www.domain.com (primary site home)
     - 404 Page
   - www.domain2.com (a second site home)
     - 404 Page
   ...

I think I heard people were using a different structure in the current old version like:

- Homepage (main site home)
   - About
   - Projects
   - 404 Page
   - www.domain2.com (second site home)
     - 404 Page
   - www.domain3.com (a third site home)
     - 404 Page
   ...

But this wasn't ever recommended and it can lead to complications.

----

Again since this module is pretty much a hack, I'm not officially supporting and releasing this module. Use at your own risk. We use it in various projects now and while it works fine with all it's little drawbacks, the new version is little more solid.

I would rather like to see if there's a way for a more integrated and supported way in the core. But not even sure how this could work out. Ryan may has some ideas or maybe thinks this isn't something PW could support. - Note that there's multisite core support, but it's for different DB's and "site" folders, but that's a different case altogether.

Take care

Soma

[joer80]

Does page->editable() work when you are on a sub website url?   My edit this page code isnt working.

I wasnt sure if it was a bug in my setup or if the code does't allow this?

I am using soma's version.

[joer80]

Ha!  Found it.

It appears if you login with www.suburl.com/admin/ it works fine on suburl.com, but if you login to mainurl.com/admin it will not print if you are on suburl.com.

I was logged into the main url and trying to edit the page on the sub url!

[justb3a]

Thanks for this module, it works even as expected in a 3.x ProcessWire installation.

But it took me a while to understand how this module works and what I have to set up. At the end it's pretty easy but I had to read 9 forum pages and failed initially by installing the wrong module. I summarized all collected information and updated the Readme file (see PR at Github), maybe someone else could benefit from this.

To prevent others from installing the old module as well, could @apeisa or someone else having access rights maybe add a litte note to the first post?

One more thing: I use MarkupSEO and got some trouble overriding the module config data for each site. Unfortunately I found no way to hook into that specific function and decided to submit a PR as well. Now I can use the following config:

$config->MultisiteDomains = array(
  'domain1.com' => array( 
    'root' => 'www.domain1.com' 
  ),
  'domain2.com' => array( 
    'root' => 'www.domain2.com', 
    'http404' => 1932,
    'markupSEO' => array(
      'piwikAnalyticsIDSite' => 12,
      'titleFormat' => '{title}'
    )
  )
);

[arjen]

Hi justb3a, thanks for your effort. A simple like didn't feel sufficient enough. I use soma's new version on several sites and didn't even consider creating a readme. Great work.

edit: and soma too offcourse for creating the new version

Edited April 21, 2016 by arjen

[Soma]

Bea, thanks so much for your work here, very appreciated! I pulled the R.  https://github.com/somatonic/Multisite/tree/dev

I'll have a go and add a note on the first post. Sorry for the confusion.

[justb3a]

Glad I could help. Here are just two litte things I noticed 

The link in the first post to the current wip version is broken. It contains %C2%A0 at the end which leads to a 404 Github page.

You can get the current dev version here
<a href="https://github.com/somatonic/Multisite/tree/dev%C2%A0" ...

The latest ProcessWire devns version 3.0.15 introduces view panels, unfortunately this module swallows them. This is no big deal, I just wanted to mention it. As soon as I uninstall the Multisite module, the panel appears instantly.

[Soma]

Glad I could help. Here are just two litte things I noticed 

The link in the first post to the current wip version is broken. It contains %C2%A0 at the end which leads to a 404 Github page.

You can get the current dev version here
<a href="https://github.com/somatonic/Multisite/tree/dev%C2%A0" ...

The latest ProcessWire devns version 3.0.15 introduces view panels, unfortunately this module swallows them. This is no big deal, I just wanted to mention it. As soon as I uninstall the Multisite module, the panel appears instantly.

Thanks for the hint, it's fixed. I thought I tested the link!

Considering this module and future development of PW. Yeah, I was playing around with that yesterday, but couldn't see a solution. Unfortunately I knew this would one day lead to complications. :/

After little experimenting I think we need to rethink $page->url rewrites Multisite does in the admin and consequently in the front-end. I always feared it was maybe dangerous/adventurous and would lead to problems sooner or later. There's so many things to consider it's crazy.

So, after long thinking and testing, I'm heading towards letting the $page->url alone, to not get in the way as much as possible.

Then we just have to make sure 2 things:

1. when an url is viewed containing a "domain" in its path that is recognized, to redirect the correct domain/url. So a view link will just work.

2. to have correct url on the front-end output, we can parse the $page->render() output and replace/fix those urls output from templates and RTE's.

This way such new features like the "View" options work out of the box. Also cross Domain linking in RTE would work also.

 

I got a test version working so far but not sure about what to further consider with this new approach.

[siilak]

Nice upgrade for a module. I tested it on latest ProcessWire DEV version and only error I get is Front-End Page Editor error.

Added a video. Maybe there is a simple solution for that

https://www.dropbox.com/s/ox5tzdkide3lrlp/error.mp4?dl=0

[nurkka]

The Multisite module (latest Version 0.0.6 from https://github.com/somatonic/Multisite/tree/dev) doesn't work correctly with the new link abstraction (since PW 3.0.6). When activated, the link abstraction feature adds the URL-parts of the Multisite-folders back to the URLs, so you'll end up with URLs like http://example.com/example.com/some-folder/some-page/ instead of http://example.com/some-folder/some-page/

I wrote a workaround, but unfortunately - since I didn't find a way to hook into the link abstraction - it's a core hack. I had to modify the methods sleepLinks() and wakeupLinks() in /wire/core/MarkupQA.php. In sleepLinks() I'm overriding the link modification, when a link points to a page, which doesn't belong to the current Multisite-branch. And in wakeupLinks() I'm stripping the Multisite-folder domain names from the given URLs. Since that doesn't make much sense in the long run, I wondered if anyone has a better solution?

@ryan Ryan, could you perhaps make the link abstraction hookable?

Or am I missing something? Every hint is very well appreciated. Thanks in advance!

[Soma]

On 19.7.2016 at 0:40 AM, siilak said:

Nice upgrade for a module. I tested it on latest ProcessWire DEV version and only error I get is Front-End Page Editor error.

Added a video. Maybe there is a simple solution for that

https://www.dropbox.com/s/ox5tzdkide3lrlp/error.mp4?dl=0

I can't reproduce this one, it's working fine here. What versions are you using? What is the error?

[siilak]

Yes, I made clean install and its ok now. I think it was my own fault.

[Soma]

15 hours ago, nurkka said:

The Multisite module (latest Version 0.0.6 from https://github.com/somatonic/Multisite/tree/dev) doesn't work correctly with the new link abstraction (since PW 3.0.6). When activated, the link abstraction feature adds the URL-parts of the Multisite-folders back to the URLs, so you'll end up with URLs like http://example.com/example.com/some-folder/some-page/ instead of http://example.com/some-folder/some-page/

I wrote a workaround, but unfortunately - since I didn't find a way to hook into the link abstraction - it's a core hack. I had to modify the methods sleepLinks() and wakeupLinks() in /wire/core/MarkupQA.php. In sleepLinks() I'm overriding the link modification, when a link points to a page, which doesn't belong to the current Multisite-branch. And in wakeupLinks() I'm stripping the Multisite-folder domain names from the given URLs. Since that doesn't make much sense in the long run, I wondered if anyone has a better solution?

@ryan Ryan, could you perhaps make the link abstraction hookable?

Or am I missing something? Every hint is very well appreciated. Thanks in advance!

Testing this, I'm not seeing any problems with what you're saying. Link abstraction works here.

Though it's an experimental feature and not sure where this leads to, same as with this module. Highly experimental.