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

Hi, 

I'm having some issues with the subdomain, the homepage of the subdomain is working but the sub pages are throwing a 404 page. I've made sure to point the domains at the same file area. I've included my config code and a screenshot of the file tree.

$config->MultisiteDomains = array(
    "codeweavers.io" => array( // domain name is used to map to root page
            "root" => "cw-home", // page name for the root page
            "http404" => 27
    ),
    "blog.codeweavers.io" => array(
            "root" => "blog",
            "http404" => 27
    )
);

I don't know if I've set something up wrong or have missed a step, but any help would be appreciated. 

Lucy

Screenshot 2019-10-22 at 09.50.49.png

Share this post


Link to post
Share on other sites
$config->httpHosts = array('codeweavers.io', 'blog.codeweavers.io');

Have you set this?

And one other thing that might be a good idea to make it more bulletproof.

Change the root names from cw-home and blog to something like lkajsd and oiquwe to avoid any future conflicts with page names. I learned this lesson some time ago.

Share this post


Link to post
Share on other sites

Hi, 

Yes, I've set the httpHosts (I forgot to add that line in).

I have changed the names of the pages to random letters and it now working! Thank you! 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
×
×
  • Create New...