Module Multisite

[benbyf]

the page is hidden.

is all abit backwards currently, I can no longer get to the multi site page as it redirects me to the homepage but with the wrong domain name.

echo "subdomain: " . $modules->Multisite->subdomain;

this gives me Home which every domain i plugin

I unhide the page and it appearded active in the menu making it look like it was home for both domains, which is very confusing

[Soma]

Well it would give you current multisite domain. As it redirects to the domain it looks like it works. If you could give access I'm sure I can figure it out.

[Soma]

I think it may cause you would not setup main homepage as root but also as multisite subfolder. Never tried a setup you have but cant say without testing and reating the code.

[MadeMyDay]

I use soma's module on different sites without problems. Some with root set as one domain, children pages with others and some with different children pages and root not defined as domain. This cannot be the problem.

[arjen]

We use the module on a lot of sites too like MadeMyDay's setup. Never had any real trouble.

[benbyf]

will try and delete the apache settings as I can't see anything else that might be wrong for that incoming domain in PW. If not I'll have to abandon the multisite and spin out to it's own PW install. Thanks for everyones help though and I'll report back

[benbyf]

server company deleted it, and now the domain doesnt even resolve anywhere even with these dns settings, feelings like im hitting my head against the wall here https://www.dropbox.com/s/m5ieinbcfzy45dy/Screenshot%202014-12-08%2012.13.53.png?dl=0

[neildaemond]

I'm I was (solution below) experiencing the same as below on PW 2.5.2, after installing via softaculus(which uses minimal site profile) on a cpanel based hosting:

Currently I'm trying to get this to work, but I'm seriously questioning if I'm using this right. What I initially thought that had to do the following steps:

1) Make sure all the traffic from www.seconddomain.com points to the home directory of the www.maindomain.com. (checked)
2) Install the module and make sure that www.seconddomain.com is added to the textarea. (checked)
3) Create a new page with the template 'home' with the title matching the domain - in this case www.seconddomain.com. Status of the page is published and hidden. (checked)

Then I thought I have to add another page to make this work:

4) Create a page with a template underneath the 'second' homepage called 'Testpage'. Status of the page is published.

I can reach the page using the following URL:
 

http://www.maindomain.com/www.seconddomain.com/testpage/

But I can't reach the page using this URL:

http://www.seconddomain.com/testpage/

Things I've noticed

1. When I try to reach www.seconddomain.com it displays a 404 error. (see below).
 

except,

When I try to reach www.seconddomain.com it displays as if I'm using www.maindomain.com

Also, http://www.seconddomain.com/www.seconddomain.com/ redirects to http://www.seconddomain.com/

SOLVED: needed to add www.seconddomain.com to $config->httpHosts in /site/config.php

[ese7en]

Hi I am using Nginx and for me your solution is not working. 

My plan was to redirect subdomains to the specific subpages the plugin was for me the best way to do this.

I added the sites named sub1.domain.com, sub2.domain.com, ... in the textarea and in the $config->httpHosts array. 

When I send the request to the sub1.domain.com I get the home page of domain.com but not to the sub1.domain.com page which is created under the root.

Is it possible that I have to change something in the Nginx Conf? 

[videokid]

Hello,

it seems I have the same problem addressed here before.

I've upgraded PW to 2.5.18, previous it was PW 2.4.1

All went well, except for the Mulltisite module... 

It's working, but not as it previously did... the links actually include the second domain

http://www.domain2.com/domain2.com/test-page/

before it was:

http://www.domain2.com/test-page/ [which return a 404 page]

which is the idea off course... also with google in mind, it's not ideal....

did I miss something somewhere?

I'm using Soma's version BTW [also tried with Apeisa's version, same thing FYI].

Greetings...

[Soma]

How is your setup?

Looks like there's maybe this issue with newline in the config textarea for domain

If you change

$this->subdomainsArray = explode("\r\n", strtolower($this->subdomains));

To

$this->subdomainsArray = explode("\n", strtolower($this->subdomains));

Does it work?

This is the code that should do a redirect when a real url containing the domain is found.

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

But even then even if the redirect isn't working the page should still show fine. Nothing there in the module that would do a 404.

The 404 seems to be an issue that the domain isn't found. But that wouldn't come from updating PW after all.

[videokid]

Wow, fast!

I've changed the line, but no effect...

oh, it's working... only the subdomain url isn't stripped and I have no idea why... 

Originally the second domain had a different template [which I called multisite_home], but somehow since the upgrade that is ignored [per default it uses 'home']. Which I don't mind actually.

Foreach domain I do have a 'homepage' call...

$homepage = $pages->get(1'); for the root

$homepage = $pages->get(1373'); for the second domain

it used to work just fine...

Thx!

Edit: deleting the domains in the module makes no difference, so I guess the module isn't working at all.... Maybe I should revert back to 2.4.x

Edit2: reverting back to 2.4.1 and everything works as expected again [will try again with an 2.5.xx later]

Edit3: reverted back the line you suggested to edit, the \r is back while textarea is being saved

Edited March 4, 2015 by videokid

[dewwwald]

I don't use MAMP, but what you have to basicly is this:

1) Install ProcessWire with for example the domain maindomain.localhost which points to /Arjen/Sites/maindomain.com/.

2) Make sure it's working fine and install the Multisite plugin.

3) Create an entry in your virtual host file and point that domain to the domain in step 1. For example point seconddomain.localhost to /Arjen/Sites/maindomain.com/ as well.

4) Now both maindomain.localhost and seconddomain.localhost will load the same website.

5) Follow instructions above.

There is no need for this complexity. If you are already using a vhost that works it might help if you simply add more server aliases to your vhost config ie. :

ServerAlias *.domain.dev

ServerAlias *.domain.dev.*.xip.io

 

for me resulting in:

 

# project-domain.dev.conf
<VirtualHost *:80>
    DocumentRoot "/home/dirr/to/server/project-name"
    ServerName project-domain.dev
    ServerAlias project-domain.dev.*.xip.io
    ServerAlias *.project-domain.dev
    ServerAlias *.project-domain.dev.*.xip.io

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    <Directory /home/dirr/to/server/project-name>
        Options FollowSymLinks
        Allow from All
        AllowOverride All
    </Directory>
</VirtualHost>

 

In my case the project-name is a symlink pointing to the root of the project,

and project-domain is the domain for the project that you added to hosts file

[arjen]

Thanks for sharing bitlinguist. You are right, there are several ways to accomplish this. In the case you can control the vhost there is indeed no need for a second vhost file since you can use an alias. The point I tried to explain (in simple steps with basic apache knowledge) is that you need two domains to point to to same server directory.

[bernhard]

hi guys!

unfortunately i can't get soma's version of the module to work. i have a vagrantbox and configured my hosts file to serve the following domains:

config.hostsupdater.aliases = ["web.dev", "multi1.web.dev", "multi2.web.dev", "web1.dev", "web2.dev", "www.web1.dev", "www.web2.dev"]

• i can reach a clean 2.6 installation via all domains
• i installed somas module
• i created 2 new pages: /home/www.web1.dev and /home/www.web2.dev
• when i visit www.web1.dev -> still the frontpage of the installation (default intermediate profile); same for www.web2.dev
• i can visit those pages via www.web1.dev/www.web1.dev/ and same for web2

i tried apeisa's version and it worked - unfortunately i did not make it to get subdomains working (site1.web.dev, site2.web.dev). but anyway i would prefer to use somas module

do you think that could be related to vagrant? unfortunately i have no live server where i can try it out at the moment...

help would be very, very appreciated!

ps: module configuration:

www.web1.dev
www.web2.dev

tried everything with and without www

[bernhard]

hey!

i have it now on my live server: same problem!

http://wemacon.eu

http://site1.wemacon.eu

http://site2.wemacon.eu

if anyone finds the time i can share admin password via PM to have a look...

[Soma]

I gladly take a look cause I have no idea what is the problem. 

Or you guys having problem could try modifiying module 

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

To this:

$this->subdomainsArray = explode("\n", strtolower($this->subdomains));

[bernhard]

thank you soma, that solved it!

for all the others: soma has already updated the module on github

[SiNNuT]

I was a bit confused at first because i did not see the update on the 'official' Github repo (apeisa/Multisite). Wouldn't it be worthwhile to add this to there?

[bernhard]

hey soma,

i did some testing the last hours and found out, that example.com/admin does NOT work while example.com/admin/ (with trailing slash) does.

not really a big problem, but maybe there is a quick and easy fix for that?

thanks again for your support - everything else working like a charm so far!

[bernhard]

i have the following problem:

www.site1.dev -> works

sub1.site1.dev -> works

but

site1.dev -> works

sub1.site1.dev -> doesn't work

any fix for this?

[Soma]

Sorry Bernhard haven't noticed your earlier posts.

I experienced something like that with the backend admin url, but not sure anymore what it was. I have a project where I use it but that is a even a newer version than the current. So I might have it already fixed there.

The other is something I see a problem with current implementation using strpos() on those domains. 

"site1.dev" is found in "sub1.site1.dev" thats why you have a problem. I'm not sure about a fix yet. I haven't got a testinstall I can play with currently, but will look into it soon. Thx.

[bernhard]

hi soma, thank you - all the problems are not time critical for now

shouldn't checking the strpos to be < 1 be enough for that?

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

if(strpos($httpHost, $subdomain) !== false AND strpos($httpHost, $subdomain) < 1) {

at least it works for me here on my dev.

but that is a even a newer version than the current

that makes me curious?!

one other thing: I'm wondering why the module does not take the valid multisite-domains from the processwire config? i always have to add new domains in both locations. ok, that's not a big deal, but i'm sure there is some more important thing behind it? any problem i don't see that could appear when "synching" multisite hosts with pw config hosts?

[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?

[LostKobrakai]

"it" is the GET parameter, what acts as access-point to ProcessWire. All requests are rewritten by the .htaccess file to something like this:

yourdomain.com/index.php?it=/subpage/moresubpages/test (see here)

Therefore it's strange that this index is undefined. It's one of few necessities in pw.