Jump to content
apeisa

Multisite

Recommended Posts

Well you just override the current page. If there are children involved you have to define those children before switching the page object. Otherwise children are empty.

Share this post


Link to post
Share on other sites

Sorry, that's gone over my head. Both the parents and children are using the same basic page template.

Share this post


Link to post
Share on other sites

Perhaps a screenshot would help with annotations which page should display what and how they are related. Also the complete code of your template would help.

Also: perhaps start a new thread, because this is pretty specific and this thread is getting longer and longer ;).

Share this post


Link to post
Share on other sites

Hi Forum,

I'm having a hard time to get the original module (Apeisa's one) to work with 2.5.

I did setup a bunch of 12 landingpages (each with a little bit different content but sharing the same template). I added their domains to the module settings as well as to $config->httpHosts array. 10 of my 12 domains were working fine, but 2 didn't - they redirected to the root. I triple checked everything but didn't find out what was wrong.

Unfortunately during this debug process I must have added a domain twice to the module settings. This made PW throw a 404 on the admin and on the frontend side for all domains making the admin inaccessible.

I've temporarily made it back into the admin by renaming the module to multisite-old.module. But I can't figure out how to "reset" the module settings to its former or a fresh state (replacing multisite.module with a new file from Github doesn't work) nor how to get all of my 12 domains work.

Any help is appreciated.

Thanks

Share this post


Link to post
Share on other sites

Hi,

I was wondering what the DNS settings for the second domain should be as I couldnt see anything obvious here.

Share this post


Link to post
Share on other sites

Anyone? I've tried forwarding the domain but that doesnt work (well in terms of the multi-site working). What would the DNS changes be?

Share this post


Link to post
Share on other sites

Make sure domain B points to the same server (A record or CNAME) as domain A. And on the serverside you have to make sure that domain B it pointing to the same directory as domain A.

  • Like 1

Share this post


Link to post
Share on other sites

OK cool. Is there any way of doing this without root access? I'm using Apache, any good links for how to set up server side? Thanks!

Share this post


Link to post
Share on other sites

Depends on your server configuration. The domainname you can alter yourself by changing the DNS. The server part you should pickup with your hosting company. If you run an unmanaged server, it (again) depends on which OS you use. A quick search on Google should help you out.

Share this post


Link to post
Share on other sites

still struggling a bit on this, is there any docs?

This is my DNS, the host has informed me its pointing the to the same directory as horton-stephens.com when incoming on hortonsshortuns.com (as i dont have root access :(

www.hortonsshortuns.com & hortonsshortuns.com set in module settings and www.hortonsshortuns.com page name for the new site. But still getting the homepage of the other site, should apache be sending to /www.hortonsshortuns.com not / ??

* A     80.87.143.6 * CNAME     www.horton-stephens....   @ MX 10   mx0.123-reg.co.uk.   @ MX 20   mx1.123-reg.co.uk. @ A     80.87.143.6   www A     80.87.143.6

Share this post


Link to post
Share on other sites

No, no. Apache has nothing to do with this module. The module only identifies the page name, does some path voodoo and that's it. No further server side configuration needed.

Your mistake is that you added several different domain names in the module's configuration. So basically it has to be configured like that:

- Homepage

-- sub page 1

-- sub page 2

[...]

-- sub site (with page name "hortonsshortuns.com")

--- sub site sub page 1

--- sub site sub page 2

--- sub site sub page 3

[...]

And in your module's config you only define "hortonsshortuns.com" as another domain. The www stuff should be configured with htaccess, but never ever put several domain variations in the module's config. This has to go wrong.

  • Like 2

Share this post


Link to post
Share on other sites

Still struggling. changed the the config to hortonsshortuns.com only and changed the title and path of the subpage to hortonsshortuns.com could there be anything else wrong with my settings above as im still only getting the home of the main site? Thanks for you help

Share this post


Link to post
Share on other sites

Hard to say... You type in hortonsshortuns.com (without www) and then you get redirected to horton-stephens.com, not to some 404 page? Do you have one (404) and are you sure you are on the homepage? You haven't changed your .htaccess I assume?

Share this post


Link to post
Share on other sites

I've not changed the .htaccess just added the above in the DNS and on the server. You don't go to a 404 (though there is one obvisouly) but just land on the home for horton-stephens.com

Share this post


Link to post
Share on other sites

Sorry, just trying to get an idea of what's going on here.

So far it sounds like your domains are configured correctly, or at least they work (mostly) as expected. The fact that hortonsshortuns.com is identical in content to www.hortonsshortuns.com and both versions work is a problem (for this module and from SEO point of view) but as long as you use the version that you've configured this module to use, it's not really the issue right now.

Anyway, this makes me think that there could be something wrong with the Multisite module config or the page it's trying to point the user to. If you're using Soma's variation of Multisite, I don't really know anything about that (never used it), but:

It might be helpful if you could post here literally how you've configured the module (every config setting and value exactly as they are on your site, either as text or screenshots)? Also, just to rule out any inconsistencies, please double-check (or triple-check, or whatever) that the related page branch is correctly named (name field, not title) and placed in the page tree below the root page, something like this:

- Home
    - whatever
    - whatever
    - hortonsshortuns.com
    - whatever
    - whatever
    - ... and so on

Looks like this has been way more difficult than it should've been, but hopefully we'll get this sorted :)

  • Like 1

Share this post


Link to post
Share on other sites

Looks ok but have no idea. Everybody seems to have problems with it except me. :)

I only used multisite on where all pages are multisites, there's no default home. But I think it doesn't matter.

What happens if you enter the direct url to the domain folder

http://domain.com/hortonsshortuns.com

What happens if you output 

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

in your template?

Maybe you can debug the module and try to locate where it's failing?

Share this post


Link to post
Share on other sites

Hey!

yeah so http://hortonsshortuns.com should redirect to http://horton-stephens.com/hortonshortuns.com but cloaked.

So I want the two sites to run off the same CMS. That not what the modules for??

The http://hortonsshortuns.com currently leads to the home of horton-stephens.com/ when it should be horton-stephens.com/hortonshortuns.com

Share this post


Link to post
Share on other sites

Yeah. It works that way.

Have you tried what I told you?

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...