Jump to content
apeisa

Multisite

Recommended Posts

Ah, I was using Apeisa's original version. Soma's version fixes the problem. Soma, you should make a pull request!

Share this post


Link to post
Share on other sites

statestreet: do you have multilang site with multilang page names?

Our needs for this module has been very little (only one site), so I would be happy to see if Soma would take a lead with his module.

Share this post


Link to post
Share on other sites

I'm not using multi-language, so I guess it must have just been something else that changed in 2.4?

Either way, thanks to both of you for creating and improving this module.

Share this post


Link to post
Share on other sites

Looks like I have a different problem now with Multisite 0.2. The original site is continuing to work fine, but we just tried launching the second site, and it displays the first site at the second site's domain. I double-checked that both lines in the module's settings screen match the titles of the top-level pages, but it still only shows the first site's content at both domains.

Share this post


Link to post
Share on other sites

@statestreet, I'm not sure but it does work fine. It's hard to tell from here. All I can say that it's not trying to match the title but the page name. Also it does have issues with that it uses strpos to find matches. Possible sideeffect would be that domain with subdomains wouldn't work I think.

domain.com

my.domain.com

would get conflict with checking for the right current domain. I think this can be fixed with having a 1:1 match checking. But not sure it's what you experience.

Although after all it's a big hack to get this multisite tree's working so it's always possible things go wrong. I still consider this a beta and while it's working I strongly recommend to only use it if you are completely aware of what it is doing. It may not suit all situations.

@apeisa, I'm not keen to take the lead on this one. I got too many modules to support already. But I'm happy to help with getting it working or fixing something.

Share this post


Link to post
Share on other sites

Although after all it's a big hack to get this multisite tree's working so it's always possible things go wrong. I still consider this a beta and while it's working I strongly recommend to only use it if you are completely aware of what it is doing. It may not suit all situations.

@apeisa, I'm not keen to take the lead on this one. I got too many modules to support already. But I'm happy to help with getting it working or fixing something.

I have just the same feelings with this one. It is highly valuable module if you need it, but approach it as a experimental.

Share this post


Link to post
Share on other sites

I finally figured this one out.

I had just about given up, when I thought to look in config.php, and lo and behold, there at the bottom was $config->httpHosts, which only contained the domains that were working. I added the other domains, and now the multisite module is working excellently.

  • Like 6

Share this post


Link to post
Share on other sites

Wao! thank you so much statestreet. You were the last piece to the puzzle. I just did a fresh install and read this entire thread.

For those who are wondering 

Follow arjen Instructions here: https://processwire.com/talk/topic/1025-multisite/#entry20399

For dev or localhost you'll need to edit your host file for your second domain name so it points to the same directory

EG.

 127.0.0.1   madbox.com

You may need to edit your virtual host when it goes live so it points to the right directory. Doesn't really matter for dev.

<VirtualHost 127.0.0.1>
ServerName sandbox.com
ServerAlias madbox.com
DocumentRoot "C:/wamp/sandbox.com"
<Directory "C:/wamp/sandbox.com">
allow from all
order allow,deny
AllowOverride All
</Directory>
</VirtualHost> 

Then in the site/config.php you'll need to edit the httpHosts variable (last one)

EG.

$config->httpHosts = array('sandbox.com', 'www.sandbox.com','www.madbox.com','madbox.com');
  • Like 2

Share this post


Link to post
Share on other sites

Your last two posts really made me hopeful to solve my issue, but unfortunately it didn`t. 

I followed the instruction of multisite module and point my traffic of test.myseconddomain.com to

mymaindomain.com/testarea/processwire.

on mymaindomain.com/testarea/processwire/test.myseconddomain.com I can reach the page.

on test.myseconddomain.com I land on the level of mymaindomain.com (basic example site) of my installation.

I am using password protection for the hidden testarea in .htaccess. I also tested if this causes problems, but it does not work either way. Also I tried to put test.myseconddomain.com into the $config->httpHosts = array() 

but then I get 404.

what is the best structure for one install with one database and several different domains and one hidden testarea? 

my PW install now is in this testarea...

thank you so much for your help!

Share this post


Link to post
Share on other sites

I need to create an offshoot site that shares some, but not all of the pages of the parent site. Is there any way to show pages from the parent site on subsite or do they have to be duplicated and made children of the subsite's home page?

Share this post


Link to post
Share on other sites

How about something like $pages->get("/www.mainsite.com/page-needed/")->render();

Of course probably not render, but outputting the fields etc.

Share this post


Link to post
Share on other sites

Thanks, that's got me going in the right direction.

Share this post


Link to post
Share on other sites

Actually, maybe not so much.

I have, for example, /about/ on the main site and I want to display the same page on the subsite. If I visit /subsite/about/ I get a 404.

Also, I've created a new template for the subsite home page which includes to a new global template (for different branding, navigation), but if I can get the same pages to show up on both main and subsites, how do I get the pages on the subsite to use the subsite global template instead of the of the main site?

Share this post


Link to post
Share on other sites

Define a field type "page", name it like "includePage" or something like that and add it to your subsite's template. If you wish to include an other page, just select it in your subsite's page. In your subsite's template just add something like this on the top:

<?php
if(count($page->includePage)>0){        // is there a page to be included?
$page = $page->includePage->eq(0);      // overwrite page fields with the included page
}

Now the $page object is overwritten with the included page object.

Share this post


Link to post
Share on other sites

So if I have:

Home

- About

- Subsite home

do you mean to include a page entry for About under Subsite home which then includes the main site's About page with the includePage fieldtype?

Share this post


Link to post
Share on other sites

exactly. Since I assume you want an 1:1 copy (regarding content) of your main site's page in a different template.

Share this post


Link to post
Share on other sites

The only problem there is they also have an ever expanding news section that they also want to duplicate so that would mean having to do this for a lot of pages.

Share this post


Link to post
Share on other sites

Well, then you have to think about some other approaches. Everything is possible.

Scenario 1: Duplicate all news:

- Use url segments. On subsite's overview list all news from main site and don't link to their url but to /subsite/news/$news->name. The /subsite/news/ overview page has url segments activated. You identify the news, include it the same way described above and you're done.

Scenario 2: Only selected news:

- Use a checkbox on the original news template and list only the news that are checked on the subsite. Rest as described in 1.

Another approach would be to use RSS for the import. As I said: Everything is possible, you only have to identify the approach which is less work for you and your client.

Share this post


Link to post
Share on other sites
<?php
if(count($page->includePage)>0){        // is there a page to be included?
$page = $page->includePage->eq(0);      // overwrite page fields with the included page
}

I'm giving this a go and it seems to work fine for first level pages, but for second level pages I get the page title but not the rest of the content.

Share this post


Link to post
Share on other sites

I also have some pages where I'm using functions and calling wire('page'). How do I update that to use the ID of the included page?

Share this post


Link to post
Share on other sites

Do you have an example? If you use them in your template there is no need for wire(). Just use $page. If you are using custom modules for your site, I am not sure. Just show your example and I will check it.

Share this post


Link to post
Share on other sites

For instance I've got something like this:

$outMain .= sponsor_row('Major Club Partners'); // $outMain is output in the global embedded template

and the function that outputs the data:

function sponsor_row($group) {
  foreach(wire('page')->sponsors as $sponsor) {
    if ($sponsor->sponsor_group->title == $group) {
      $output .= …
    }
  }
  return $output;
}

Share this post


Link to post
Share on other sites

Well, your function also should work like this (assuming it is defined in your template):

function sponsor_row($group) {
  foreach($page->sponsors as $sponsor) {
    if ($sponsor->sponsor_group->title == $group) {
      $output .= …
    }
  }
  return $output;
}

Otherwise I need to know the environment. You also could handle over the $page object:

$outMain .= sponsor_row('Major Club Partners',$page);
function sponsor_row($group, $page) {
  foreach($page->sponsors as $sponsor) {
    if ($sponsor->sponsor_group->title == $group) {
      $output .= …
    }
  }
  return $output;
}

Share this post


Link to post
Share on other sites

Actually, just tried

$outMain .= sponsor_row('Major Club Partners,$page');

and that's working fine. :)

Now I just need to know why my second level pages aren't outputting any content.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

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

Create an account

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

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By 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 Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • 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-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
×
×
  • Create New...