Jump to content
apeisa

Multisite

Recommended Posts

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.

Share this post


Link to post
Share on other sites

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

  • Like 1

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

  • Like 3

Share this post


Link to post
Share on other sites

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 :) 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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 :)

Share this post


Link to post
Share on other sites

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?! :)

Share this post


Link to post
Share on other sites

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

  • Like 6

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

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}'
    )
  )
);
  • Like 9

Share this post


Link to post
Share on other sites

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 by arjen
  • Like 5

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.
  • Like 4

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites
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?

  • Like 1

Share this post


Link to post
Share on other sites
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.

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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful, developer-first 3rd party 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! 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-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 If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      Please have a look at the screenshots to get an idea what I'm talking about (open spoiler):
      (Please note: these screenshots are from an early development state of SnipWire. To see actual screens please have a look at later posts below!)
       
    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...