Jump to content
apeisa

Multisite

Recommended Posts

@Soma in your README, at the bottom, you write:
 

Quote

Since the whole concept is all a pretty hack, I found that it comes with some complications that can't be solved in an 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 Multisite. So you'll end with wrong URL's when for example you 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.

I was doing a few tests just now. For me, it all works wonderfully (well, at least in a local setup). Did you change something recently in that regard and forgot to edit the readme?
 

Share this post


Link to post
Share on other sites
16 hours ago, dragan said:

@Soma in your README, at the bottom, you write:
 

I was doing a few tests just now. For me, it all works wonderfully (well, at least in a local setup). Did you change something recently in that regard and forgot to edit the readme?
 

Yeah that's not anymore. There's a parser on page render now.

Share this post


Link to post
Share on other sites

The module is working otherwise great (thanks a lot!), but when visiting www. subdomain, the URLs of the rootParent children lack the domain.

$siteRoot = $page->rootParent;
$nav = "";
foreach ($siteRoot->children as $child) {
  $nav .= "<a href='$child->url'>$child->title</a>\n";
}

This produces urls like https://pagename

I can use <a href='/$child->name'> instead to make them work as relative URLs, but it would be nice to know what is going wrong.

Setup:

- Home
  - mysite.com
  - myothersite.com

$config->MultisiteDomains = array(
    "mysite.com" => array(
            "root" => "mysite.com",
            "http404" => 27
        ),
    "www.mysite.com" => array(
            "root" => "mysite.com",
            "http404" => 27
        ),
    "myothersite.com" => array(
            "root" => "myothersite.com",
            "http404" => 1017
        ),
    "www.myothersite.com" => array(
            "root" => "myothersite.com",
            "http404" => 1017
        )
);
$config->httpHosts = array('mysite.com','www.mysite.com','myothersite.com','www.myothersite.com');

If I don't have the separate www. entries in MultisiteDomains, it does not work. It just throws me to the "Home" page, if I try to navigate to www. subdomain.

Share this post


Link to post
Share on other sites

Maybe I'm missing something here but I ran into minor problems setting this up for domains that contain a hyphen.

First of all the setup is multisite AND multilanguage.
PW 3.0.130, Multisite Module from Github, 3 domains, 2 languages

Link from ProcessWire Backend: http://abelt.test/en/alexander-abelt.test/ gets wrongly redirected to http://abelt.test/en/alexander- and not to http://alexander-abelt.test/en/.

In this case it's not a real deal-breaker as it's only a setup I need for some of my domains and I know how to work around this but nonetheless I'd like to know if I have to change something or if it is a hiccup here.

Share this post


Link to post
Share on other sites
5 minutes ago, wbmnfktr said:

Maybe I'm missing something here but I ran into minor problems setting this up for domains that contain a hyphen.

First of all the setup is multisite AND multilanguage.
PW 3.0.130, Multisite Module from Github, 3 domains, 2 languages

Link from ProcessWire Backend: http://abelt.test/en/alexander-abelt.test/ gets wrongly redirected to http://abelt.test/en/alexander- and not to http://alexander-abelt.test/en/.

In this case it's not a real deal-breaker as it's only a setup I need for some of my domains and I know how to work around this but nonetheless I'd like to know if I have to change something or if it is a hiccup here.

I think this can happen if your multisite root page name has also the domain name in it. You should avoid that. Just rename it to something else

 

On 3/31/2019 at 9:34 PM, Beluga said:

The module is working otherwise great (thanks a lot!), but when visiting www. subdomain, the URLs of the rootParent children lack the domain.


$siteRoot = $page->rootParent;
$nav = "";
foreach ($siteRoot->children as $child) {
  $nav .= "<a href='$child->url'>$child->title</a>\n";
}

This produces urls like https://pagename

I can use <a href='/$child->name'> instead to make them work as relative URLs, but it would be nice to know what is going wrong.

Setup:

- Home
  - mysite.com
  - myothersite.com


$config->MultisiteDomains = array(
    "mysite.com" => array(
            "root" => "mysite.com",
            "http404" => 27
        ),
    "www.mysite.com" => array(
            "root" => "mysite.com",
            "http404" => 27
        ),
    "myothersite.com" => array(
            "root" => "myothersite.com",
            "http404" => 1017
        ),
    "www.myothersite.com" => array(
            "root" => "myothersite.com",
            "http404" => 1017
        )
);

$config->httpHosts = array('mysite.com','www.mysite.com','myothersite.com','www.myothersite.com');

If I don't have the separate www. entries in MultisiteDomains, it does not work. It just throws me to the "Home" page, if I try to navigate to www. subdomain.

My guess is that this comes from the fact you have domain.com and www.domain.com. You want to avoid that, cause the script isn't clever enough to know which is which. In any case you want to avoid having two domains setup for the same site. You should redirect your www to non www or the other way around.

  • Like 1

Share this post


Link to post
Share on other sites
4 minutes ago, Soma said:

I think this can happen if your multisite root page name has also the domain name in it. You should avoid that. Just rename it to something else

Ok... I see the problem.

alexander-abelt.test shares one of the other domains abelt.test in it which I can't really avoid as these are or will be my domains (just with another .tld of course) I want to use later on.

As this has no further effects on maintaining content, building menus and whatever so far I guess I can ignore that linking/redirecting issue for now.

Thanks for pointing that out.

Share this post


Link to post
Share on other sites

Ah reading againg. 

9 minutes ago, wbmnfktr said:

Ok... I see the problem.

alexander-abelt.test shares one of the other domains abelt.test in it which I can't really avoid as these are or will be my domains (just with another .tld of course) I want to use later on.

As this has no further effects on maintaining content, building menus and whatever so far I guess I can ignore that linking/redirecting issue for now.

Thanks for pointing that out.

Ah reading again, I'm not 100% sure why this happens in your case. (but most likely what i said anyway :)) What is the setup config? And what Module version?

Share this post


Link to post
Share on other sites
2 minutes ago, Soma said:

but most likely what i said anyway 🙂

It works aside from that redirect issue so... I guess I will survive. 😉 

2 minutes ago, Soma said:

What is the setup config? And what Module version?

PW 3.0.130, Multisite Module from Github (says 0.1.2), 3 domains, 2 languages on Linux (Ubuntu), Apache 2.4, PHP 7.2

Page tree:

Screenshot-20190507-151451.png.2ed4cfd809345aba190eb75fd278f6e6.png

config.php

$config->MultisiteDomains = array(
    "abelt.test" => array( // domain name is used to map to root page
            "root" => "abelt.test", // page name for the root page
            "http404" => 1031
        ),
    "alexander-abelt.test" => array( // funktioniert nicht mit /en/ auf Home
            "root" => "alexander-abelt.test",
            "http404" => 1029
        ),
    "kettenburg14.test" => array(
            "root" => "kettenburg14.test",
            "http404" => 1030
        )
);

$config->httpHosts = array('abelt.test', 'alexander-abelt.test', 'kettenburg14.test');
// $config->httpHosts = array_keys($config->MultisiteDomains);

 

Share this post


Link to post
Share on other sites
4 minutes ago, wbmnfktr said:

It works aside from that redirect issue so... I guess I will survive. 😉 

PW 3.0.130, Multisite Module from Github (says 0.1.2), 3 domains, 2 languages on Linux (Ubuntu), Apache 2.4, PHP 7.2

Page tree:

Screenshot-20190507-151451.png.2ed4cfd809345aba190eb75fd278f6e6.png

config.php


$config->MultisiteDomains = array(
    "abelt.test" => array( // domain name is used to map to root page
            "root" => "abelt.test", // page name for the root page
            "http404" => 1031
        ),
    "alexander-abelt.test" => array( // funktioniert nicht mit /en/ auf Home
            "root" => "alexander-abelt.test",
            "http404" => 1029
        ),
    "kettenburg14.test" => array(
            "root" => "kettenburg14.test",
            "http404" => 1030
        )
);

$config->httpHosts = array('abelt.test', 'alexander-abelt.test', 'kettenburg14.test');
// $config->httpHosts = array_keys($config->MultisiteDomains);

 

Yes the problem is most likely that both sites share the same names in it.

abelt.test is in both setups and even in the root name. Just rename the root to something else more unique would do the trick. It's not something you would see anyway. 

"abelt.test" => array( // domain name is used to map to root page
            "root" => "abelt", // page name for the root page
            "http404" => 1031
        ),
    "alexander-abelt.test" => array( // funktioniert nicht mit /en/ auf Home
            "root" => "alexander",
            "http404" => 1029
        ),
  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

That did the trick perfectly!

Changing root and the page names fixed it. Didn't really get that the page's name doesn't have to be the domain actually.

Share this post


Link to post
Share on other sites

An additional sitenote here:

Changing the root name to something different than the domain is not enough.
If that page name appears anywhere else at the end of an URL the hiccup is back.

root = abelt
Problematic page URL = /about-abelt/ 
Problematic page URL = /about/abelt/
Working page URL = /about-abelt-whatever/

As to make sure I don't run into any issues with this I changed my root page names to something a cat would write while walking over the keyboard.

An additional sitenote here:

Changing the root name to something different than the domain is not enough.
If that page name appears anywhere else at the end of an URL the hiccup is back.

root = abelt
Problematic page URL = /about-abelt/ 
Problematic page URL = /about/abelt/
Working page URL = /about-abelt-whatever/

As to make sure I don't run into any issues with this I changed my root page names to something a cat would write while walking over the keyboard.

Share this post


Link to post
Share on other sites
21 minutes ago, wbmnfktr said:

An additional sitenote here:

Changing the root name to something different than the domain is not enough.
If that page name appears anywhere else at the end of an URL the hiccup is back.

root = abelt
Problematic page URL = /about-abelt/ 
Problematic page URL = /about/abelt/
Working page URL = /about-abelt-whatever/

As to make sure I don't run into any issues with this I changed my root page names to something a cat would write while walking over the keyboard.

An additional sitenote here:

Changing the root name to something different than the domain is not enough.
If that page name appears anywhere else at the end of an URL the hiccup is back.

root = abelt
Problematic page URL = /about-abelt/ 
Problematic page URL = /about/abelt/
Working page URL = /about-abelt-whatever/

As to make sure I don't run into any issues with this I changed my root page names to something a cat would write while walking over the keyboard.

I don't have cats 😛

Yes that's true. I know the "redirect if domain name is found in url" would need even a much more sophisticated parsing method, but it gets too complicated for my brain. I think having random strings as root name would be a much easier solution.

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, Soma said:

I don't have cats

That could become a problem then. You should add it as a requirement to the module nonetheless. 😉

2 minutes ago, Soma said:

would need even a much more sophisticated parsing method, but it gets too complicated for my brain.

Not needed when everything was set up correctly with this things in mind. You know about that and do the necessary things. I'm relatively new to this setup and had to work through this. Now I know too.

2 minutes ago, Soma said:

I think having random strings as root name would be a much easier solution.

It is. Actually it could make other things easier when debugging. As I see some weird strings instead of domain(.tld) now I don't falsely think of domain names and such things. I know right away it's something different and where it comes from.

Share this post


Link to post
Share on other sites

How do you guys handle developing on local machines regarding Multisite? Often I download the production database and I have different config.php, but I'm starting to dislike that approach 🙂 I can off course put all the environment stuff in an .ini and read with parse_ini. 

$config->MultisiteDomains = array(
    'www.realdomain.com' => array(
            'root' => 'www.realdomain.com',
            'http404' => 1045
        ),
    'realdomain.localhost' => array(
            'root' => 'realdomain.localhost',
            'http404' => 1045
        ),
    'www.anotherrealdomain.com' => array(
            'root' => 'www.anotherrealdomain.com',
            'http404' => 1046
        ),
    'anotherrealdomain.localhost' => array(
            'root' => 'anotherrealdomain.localhost',
            'http404' => 1046
        ),
  );

I have a lot of domains in the multisite. Would love to hear your approaches.  

Share this post


Link to post
Share on other sites
8 minutes ago, arjen said:

How do you guys handle developing on local machines regarding Multisite? Often I download the production database and I have different config.php, but I'm starting to dislike that approach 🙂


$config->MultisiteDomains = array(
    'www.realdomain.com' => array(
            'root' => 'www.realdomain.com',
            'http404' => 1045
        ),
    'realdomain.localhost' => array(
            'root' => 'realdomain.localhost',
            'http404' => 1045
        ),
    'www.anotherrealdomain.com' => array(
            'root' => 'www.anotherrealdomain.com',
            'http404' => 1046
        ),
    'anotherrealdomain.localhost' => array(
            'root' => 'anotherrealdomain.localhost',
            'http404' => 1046
        ),
  );

I have a lot of domains in the multisite. Would love to hear your approaches.  

I have a config-dev.php for dev server or local setup. and the "root" stays the same just the domains are different.

  • Like 1

Share this post


Link to post
Share on other sites

Ah, the good old -dev approach. That might work here too. I used to have it everywhere, but I've switched to more generic config.php which reads a config.ini which is outside my version control. The big disadvantage here is when you have a lot of customisations in your config.php. Thanks for reminding me.

Share this post


Link to post
Share on other sites

We have a local config.env.php file which is read by our general config.php.

Everything that is commun is in config.php, but local settings are kept in config.env.php.

In config.php:

/**
 * Environment configuration file
 * 
 */
$configFile = $config->paths->site . 'config.env.php';
 
 @require_once($configFile);
  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, arjen said:

How do you guys handle developing on local machines regarding Multisite?

You can also edit your local HOSTS file, so the domains always stay the same. Just remember to comment your hosts file when working on the live site 🙂

  • Like 1

Share this post


Link to post
Share on other sites

@apeisa @Soma

Just noticed that the modules directory entry for this module still points to the old repository, and also doesn't list Multisite as being PW3.x compatible. Would it make sense to update the entry to point to Soma's repository?

We just did a similar shift for AdminBar, and Adrian made the necessary changes in the modules repo.

Also, I'm currently not entirely sure which branch I should use – last I checked it seemed that "dev" was the one to use, but since then that has apparently been removed (or renamed) and now there are two branches left: master and dev2. Master is the one with most recent updates, so is that preferred over dev2, or vice versa?

Sorry for all the silly questions 🙂

  • Like 2

Share this post


Link to post
Share on other sites

Totally OK for me. Another module that I haven't had use in about 5 years... 

Share this post


Link to post
Share on other sites
On 7/20/2019 at 10:18 PM, teppo said:

Also, I'm currently not entirely sure which branch I should use – last I checked it seemed that "dev" was the one to use, but since then that has apparently been removed (or renamed) and now there are two branches left: master and dev2. Master is the one with most recent updates, so is that preferred over dev2, or vice versa?

I also have this question. Which is the recommended branch to use? @Soma

Share this post


Link to post
Share on other sites

The dev2 I made to the master couple months ago. So the new commit is just a minor addition to the url parser. I think I had difficulties with making the dev2 to master and I couldn't delete the dev2 branch. 😢

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      Why?
      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Installation
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. Field widths entered into the Template Field Widths inputfield are only applied if the Edit Template form is submitted with the Template Field Widths inputfield in an opened state. "Collapsed" is the recommended setting if you think you might also use core inputs for setting field widths in a template context. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
      https://github.com/Toutouwai/TemplateFieldWidths
      https://modules.processwire.com/modules/template-field-widths/
    • By adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

       
      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
    • By adrian
      This module allows you to automatically rename file (including image) uploads according to a configurable format
      This module lets you define as many rules as you need to determine how uploaded files will be named and you can have different rules for different pages, templates, fields, and file extensions, or one rule for all uploads. Renaming works for files uploaded via the admin interface and also via the API, including images added from remote URLs.   Github: https://github.com/adrianbj/CustomUploadNames
      Modules Directory: http://modules.processwire.com/modules/process-custom-upload-names/
      Renaming Rules
      The module config allows you to set an unlimited number of Rename Rules. You can define rules to specific fields, templates, pages, and file extensions. If a rule option is left blank, the rule with be applied to all fields/templates/pages/extensions. Leave Filename Format blank to prevent renaming for a specific field/template/page combo, overriding a more general rule. Rules are processed in order, so put more specific rules before more general ones. You can drag to change the order of rules as needed. The following variables can be used in the filename format: $page, $template, $field, and $file. For some of these (eg. $field->description), if they haven't been filled out and saved prior to uploading the image, renaming won't occur on upload, but will happen on page save (could be an issue if image has already been inserted into RTE/HTML field before page save). Some examples: $page->title mysite-{$template->name}-images $field->label $file->description {$page->name}-{$file->filesize}-kb prefix-[Y-m-d_H-i-s]-suffix (anything inside square brackets is is considered to be a PHP date format for the current date/time) randstring[n] (where n is the number of characters you want in the string) ### (custom number mask, eg. 001 if more than one image with same name on a page. This is an enhanced version of the automatic addition of numbers if required) If 'Rename on Save' is checked files will be renamed again each time a page is saved (admin or front-end via API). WARNING: this setting will break any direct links to the old filename, which is particularly relevant for images inserted into RTE/HTML fields. The Filename Format can be defined using plain text and PW $page variable, for example: mysite-{$page->path} You can preserve the uploaded filename for certain rules. This will allow you to set a general renaming rule for your entire site, but then add a rule for a specific page/template/field that does not rename the uploaded file. Just simply build the rule, but leave the Filename Format field empty. You can specify an optional character limit (to nearest whole word) for the length of the filename - useful if you are using $page->path, $path->name etc and have very long page names - eg. news articles, publication titles etc. NOTE - if you are using ProcessWire's webp features, be sure to use the useSrcExt because if you have jpg and png files on the same page and your rename rules result in the same name, you need to maintain the src extension so they are kept as separate files.
      $config->webpOptions = array(     'useSrcExt' => false, // Use source file extension in webp filename? (file.jpg.webp rather than file.webp) ); Acknowledgments
      The module config settings make use of code from Pete's EmailToPage module and the renaming function is based on this code from Ryan: http://processwire.com/talk/topic/3299-ability-to-define-convention-for-image-and-file-upload-names/?p=32623 (also see this post for his thoughts on file renaming and why it is the lazy way out - worth a read before deciding to use this module). 
       
       
      NOTE:
      This should not be needed on most sites, but I work with lots of sites that host PDFs and photos/vectors that are available for download and I have always renamed the files on upload because clients will often upload files with horrible meaningless filenames like:
      Final ReportV6 web version for John Feb 23.PDF

×
×
  • Create New...