Jump to content
apeisa

Multisite

Recommended Posts

the page is hidden.

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

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

this gives me Home which every domain i plugin


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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

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

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

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

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

I can reach the page using the following URL:
 

http://www.maindomain.com/www.seconddomain.com/testpage/
But I can't reach the page using this URL:

http://www.seconddomain.com/testpage/
Things I've noticed

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

except,

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

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

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

  • Like 2

Share this post


Link to post
Share on other sites

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

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

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

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

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

Share this post


Link to post
Share on other sites

Hello,

it seems I have the same problem addressed here before.

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

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

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

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

before it was:

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

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

did I miss something somewhere?

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

Greetings...

Share this post


Link to post
Share on other sites

How is your setup?

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

If you change

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

To

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

Does it work?

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

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

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

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

  • Like 1

Share this post


Link to post
Share on other sites

Wow, fast!

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

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

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

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

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

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

it used to work just fine...

Thx!

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

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

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

Edited by videokid

Share this post


Link to post
Share on other sites

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

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

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

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

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

5) Follow instructions above.

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

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

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

    <Directory /home/dirr/to/server/project-name>
        Options FollowSymLinks
        Allow from All
        AllowOverride All
    </Directory>
</VirtualHost>
 
In my case the project-name is a symlink pointing to the root of the project,
and project-domain is the domain for the project that you added to hosts file

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

hi guys!

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

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

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

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

help would be very, very appreciated!

ps: module configuration:

www.web1.dev
www.web2.dev

tried everything with and without www

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

hey soma,

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

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

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

Share this post


Link to post
Share on other sites

i have the following problem:

www.site1.dev -> works

sub1.site1.dev -> works

but

site1.dev -> works

sub1.site1.dev -> doesn't work

any fix for this?

Share this post


Link to post
Share on other sites

Sorry Bernhard haven't noticed your earlier posts.

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

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

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

  • Like 1

Share this post


Link to post
Share on other sites

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

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

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

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

at least it works for me here on my dev.

but that is a even a newer version than the current

that makes me curious?! ;)

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

Share this post


Link to post
Share on other sites

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

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

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

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 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-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 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 (alpha version only available via GitHub) 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 ----
       
    • 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...