Jump to content

Multisite


apeisa

Recommended Posts

(Added by Soma)

Note that this module is deprecated.

The newer and more maintained version is found here:

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

You can get the current dev version here https://github.com/somatonic/Multisite/tree/dev

(Original Post)

Just pushed simple multisite module to github: https://github.com/a...ultisite.module


What this module does?
It allows you to run multiple sites with different domains run from single install, using same database. While you can easily do "subsites" like www.domain.com/campaign/, this allows you to turn that into www.campaign.com. This is nice stuff, when you have multiple simple sites, that all belong to same organisation and same people maintain.

How to use it?
Just create page with name like www.campaigndomain.com under your homepage, then edit this module through modules menu and add same domain there. If your domain resolves to same place where your main domain, it should just work. Please notice that if you have editing rights, it allows you to browse the site from www.olddomain.com/www.campaigndomain.com/, but users with no editing rights are redirected to www.campaigndomain.com (this is because session cookie is otherwise lost).

Any problems?
Not any real problems, at least yet known. Of course think twice when deciding should the site have own install instead of this. There are few benefits, like getting data from other sites, one admin view for all sites etc... but it can easily get out of the hands: number of templates, fields etc.. It is harder to maintain for sure.

Isn't there multisite support in core?
Yes, kind of. It is very different from this. It allows you to run multiple pw-installations with shared core files (/wire/ folder). This is totally different: this is single pw-installation which has multiple sites running from different domains.



This is basically just a wrapper with one config field for this little snippet Ryan posted here: http://processwire.c...ndpost__p__5578 (so most of the credit goes to Mr. Cramer here). What it also does is that it manipulates $page->path / url properties to have right subdomain value.

  • Like 9
Link to comment
Share on other sites

Antti, this looks fantastic. I'm pointing another domain to processwire.com so that I can test this out.

One suggestion that I have is to change this:

// If subdomain is visible on url, we might wanna redirect
if(strpos($_GET['it'],$subdomain) !== false) {
   // We don't redirect if one has editing access (because user would need to login on new domain also)
   $page = $this->pages->get("/". $_GET['it']);
   if(!$page->editable()) {
       $_GET['it'] = str_replace("{$subdomain}/", "", $_GET['it']);
       $this->session->redirect('http://' . $subdomain . '/' . $_GET['it']);
   }
}

…to this (or something like it, as I've not actually tested, but hopefully the intention is there): :)

// saved $_GET['it'], since PW unsets it after using it
// note this is an unsanitized variable, so only look at it, don't use it
protected $it;

public function init() { 
   $this->subdomainsArray = explode("\n", strtolower($this->subdomains));
   $this->it = ltrim($_GET['it'], '/');

   // ...then your existing code…

}

public function ready() {
   // if $this->subdomain was valid in init(), then no need to do more here.
   if($this->subdomain) return; 

   $subdomain = $this->page->rootParent->name; 
   // if rootParent->name isn't a subdomain, then no need to continue
   if(!in_array($subdomain, $this->subdomainsArray)) return;

   // if subdomain is visible on url, we might wanna redirect
   if(strpos($this->it, $subdomain) === 0 && !$this->page->editable()) { 
    $url = str_replace("/{$subdomain}/", '/', $this->page->httpUrl);
    $this->session->redirect(url); 
   }
}

The point of this is to avoid sending an unfiltered $_GET['it'] into $pages->get(), which may contain anything in it at that point. There's always a security concern with sending unfiltered input to any function that isn't expecting it. You can avoid the issue completely by moving the check into the ready() function, which gets called after PW has already validated the URL and determined the page. If you wanted to get more fancy with it, you could also foreach($input->urlSegments) and append $input->pageNum (if > 1), but I really don't think that's necessary.

  • Like 1
Link to comment
Share on other sites

Nice, apeisa. Some multisite features would be a great enhancement for PW. For example to provide a mobile site using a subdomain. So this is a nice step forward here. I have been experimenting on something like this several weeks ago, too, but then had to focus on some other modules. So I’m curious about your ideas.

Link to comment
Share on other sites

Ryan, thanks for suggestion. For some reason I thought that $_GET['it'] has only path values like /fdas/asd/ (like htaccess wouldn't send it to pw otherwise) but of course that isn't the case (we can have get parameters in url). I will update my code soon.

Oliver: you could definitely use this for m.domain.com type of stuff, actually a great use case for this module also. Many of our clients tend to have multiple smaller sites, that need to use data from main site, are maintained by same people, but usually have different marketing domain and own visuals. That is the original need for this module, but actually I would probably use this for m.domain.com type of mobile versions also.

Link to comment
Share on other sites

  • 1 month later...

Hi Atti, thanks for your module! I am a bit confused about the usage, though... How am I supposed to access the backend? The module rewrites the URL so I can access my pages under the domain page, but the admin page can't be moved inside this domain page. But without that I cannot access it because the URL domain.com/processwire/ is catched by the module and tries to redirect to domain.com/domain.com/processwire which fails.

Thx for help!

edit: I changed line 40 into:

if(strpos($httpHost, $subdomain) !== false && strpos($httpHost, 'admin') !== false) {

which works for now. But I think this is not intended, so I would appreciate the "proper" solution ;-)

Another edit: How is the homepage supposed to work? Now it is the root page, but with several domains it would be nice to have several homepages (under the domain page or the domain page itself). What do you think?

Edited by MadeMyDay
Link to comment
Share on other sites

This is how we use this:

www.maindomain.com // This is the mainsite, runs just like any other pw-site

www.campaign.com // This is the first one using multisite, this domain is entered into module settings, but also as page under maindomain.com

www.anothercampaign.com // Just like the above

Admin for all these pages is accessible from www.maindomain.com/processwire/

First level of site tree from maindomain.com looks like this:

  • About Us
  • News
  • Contact us
  • Sitemap
  • www.campaign.com (hidden)
  • www.anothercampaign.com (hidden)

I won't suggest building very complicated setups with this, but it is superb for few specific campaign sites (especially if same people maintain or they reuse the data between). If you have many big sites under same site, you will end up with huge amount of templates & fields.

  • Like 1
Link to comment
Share on other sites

  • 5 months later...

I would like to ask if it could be possible for a site with this module to have "the same" pages urls or processwire won't allow it to be made in any way? What I mean by "the same" is domain.com/particular-page and domain.net/particular-page or m.domain.com/particular-page. It would be very useful ie in case of desktop and mobile websites.

So I suppose the question is if page in ProcessWire has to have unique Name or we might have got pages with the same names under different "Categories".

website.com/race1/first-place

website.com/race1/second-place

website.com/race2/first-place

website.com/race2/second-place

?

Link to comment
Share on other sites

I am not sure I fully understand your question. Page name needs to be unique only among siblings. So your described page-tree is perfectly valid.

If you were asking if this module is suitable for offering same content for differend devices, then it is not intention of this module and that could be done in template level.

Link to comment
Share on other sites

Ok, I just rechecked and everything is working fine. So sorry for unnecessary question. I must have been very asleep when messing with it this night. I was doing stupid mistake - cloning a page and wanting to set the same name without moving it in a tree earlier. But if I didn't ask I probably wouldn't check it again.

Thanks :)

Link to comment
Share on other sites

  • 3 weeks later...

@apeisa, thanks for this module -- it's working beautifully!

For our needs I had to implement support for alternative domains (each extra domain can have n alternatives, which all point to the same location.) With separate domains for development and secure addresses -- not to mention that in this case the client required alternative domains that couldn't be handled very well with just redirects -- that was pretty much the easiest way to put together a consistent experience.

So, basically I'm asking if you'd be interested in incorporating that addition in the main module if I sent you a pull request for it (of course once I've tested it properly first?) :)

Link to comment
Share on other sites

  • 4 weeks later...

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.

2. The other items (like the primary navigation) on rootlevel are changed to www.seconddomain.com.

Thinking

Then I starting thinking (just about then ;) ): is this supposed to work like this?

The idea

I got a very simple site with three pages and the client really liked to the idea to create some landing pages using other domains but using the same structure. Hence I thought apeisa's Multisite could be used here.

Many thanks for any thoughts!

Link to comment
Share on other sites

Arjen, sorry to hear about problems. Your setup seems right to me.

Just to confirm: if you do remove the domain from module settings, you can use www.seconddomain.com and browse the "root site" normally? Also www.maindomain.com/www.seconddomain.com/ works and you can access that page normally?

Then if you try www.seconddomain.com is the 404 error msg generated by PW or Apache? Does the module do any redirects? What is visible on addressbar? Feel free to PM me any additional details if you want me to take closer look.

Link to comment
Share on other sites

If I remove the domain from the module setting I can browse the root site normally.

If I browse:

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

it loads the seconddomain homepage.

The 404 error is generated by PW. It doesn't redirect when I try to reach:

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

I am using this with some subdomains. Could that be the issue here? The root site is located at:

http://clientdomainname.clients.mysite.com/

I will PM you in a short moment.

Link to comment
Share on other sites

Hi,

with Options #1: multiple sites with multiple databases how

Sites can't easily share data with each other, since they are running independently from one another.

is hard?

I've 4 sites:

HQ (advertising and redirect to one of the children, in the future this control the newsletter sending operation and the main events calendar)

\_ site2

\_ site3

\_ site4

Site2 have the most users and contents.

Sites 2,3,4 can share a couple of "translator user".

HQ news/events must be viewed also in 2, 3 and 4.

Site2 specific news/events must be viewed in HQ, 3 and 4.

Only this.

Thanks,

Marco

Link to comment
Share on other sites

Unless I misunderstand, i think the answer is actually the module that this thread is about. Option 1 is for multiple databases that don't share data. Option 2 (this module) is the one you'd want with multiple sites sharing data.

Link to comment
Share on other sites

Hi Ryan,

you are right.

All ok, but in the pros and cons docs says can't easily, so I imagine that this can be done.

Which is the best way to have private database and template but share few info (e.g. global news) between the sites?

Link to comment
Share on other sites

Which is the best way to have private database and template but share few info (e.g. global news) between the sites?

The problem with having multiple sites pulling and/or manipulating from the same database is that the two sites become dependent upon one another. If something needs to change with the data source, then both sites need to change. If one site becomes compromised, both sites are compromised.

When two sites need to talk to each other, regardless of platform, the best practice is to use JSON or XML web services.

For the example you mentioned, and in the context of ProcessWire, I would use RSS feeds. Generate a feed of the data you want to share using the RSS Feed Generator module. Then output it on another site using the RSS Feed Loader module. Now you have two sites easily sharing data in a bulletproof manner.

For more complex needs, you might also want to check out the Pages Web Service module.

  • Like 2
Link to comment
Share on other sites

  • 1 month later...

I have a website where the multisite module by apeia is running smoothly. One thing I can't get to work is how to share accounts on multiple sites. I've created an extra role called 'subscriber'. When I check:

if ($user->hasRole("subscriber")) {
echo "This is a subscriber.";
}

It's echoed on the mainsite.com, but it returns nothing (empty) on the otherdomain.com.

Then I checked:

echo $user->name;

It returns the $user->name on the mainsite.com, but again empty (actually guest) on the otherdomain.com.

Is this a session thing? Any thoughts on how to make a user who is logged in on the mainsite.com is also logged in on the subdomain.com?

Thanks!

Link to comment
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 Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Screenshots
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Advanced
      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
      https://github.com/Toutouwai/CustomAdminMenus
      https://processwire.com/modules/custom-admin-menus/
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      Settings
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      https://processwire.com/modules/login-fail-notifier/
      Link to github.com:
      https://github.com/techcnet/LoginFailNotifier
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
       
      Requirements:
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
×
×
  • Create New...