Jump to content
apeisa

Multisite

Recommended Posts

Will brush up my github forking skills.

Share this post


Link to post
Share on other sites

Thank you Arjen, it works perfectly. I guess your PHP skills are a bit more advanced than mine ;)

Share this post


Link to post
Share on other sites

You're welcome. Please keep in mind that this works for me on my local server, but the code may need some working on for use on production sites.

Share this post


Link to post
Share on other sites

I noticed the first problems with Form Builder today. Apeisa wrote this module would work with Form Builder if you create one /form-builder/ page under each of my subsites.

However, if I embed a form, ProcessWire always points the IFrame to the first existing /form-builder/ page in the tree.

So if I have the following sites and embed a form on the second contact page, Form Builder tries to load

events.riez.pw/openair.riez.pw/form-builder/contact/

Does anyone have an approach how to fix this behavior  :( ?

riez.pw
-- openair.riez.pw
---- Form Builder
---- Contact
-- events.riez.pw
---- Form Builder
---- Contact
 
  • Maybe not compatible with all the modules. Ie. form builder works, but you need to create new /form-builder/ page under each of your subsites.

Sorry if this post belongs to the FormBuilder forum, but I do not have access to it, yet.

Share this post


Link to post
Share on other sites

Nope, sorry ezeey. I also want to use FormBuilder on the subsites, so I'm going to check this out. Finally got a chance to test my alteration and it didn't seem to break anything on the live site.

Share this post


Link to post
Share on other sites

ezeey, I don't understand how it works for you. Any live example I can go take a look? I am using form builder with multisite and it is working fine. I have copied the form-builder page under each subsite but also under the main site.

Share this post


Link to post
Share on other sites

ezeey, I don't understand how it works for you. Any live example I can go take a look? I am using form builder with multisite and it is working fine. I have copied the form-builder page under each subsite but also under the main site.

Hi apeisa,

I just uploaded the current version page I am working on to my server. I configured FormBuilder exactly as you describe: One FormBuilder page under the root, and one more under each subsite. Strangely it seems to work for one of the subsites but not for the others.

Would you take a look at it? What data do you need from me?

Thank you again for your help!

Share this post


Link to post
Share on other sites

I think urls and admin login would be enough at this point. I am happy to take a look.

  • Like 1

Share this post


Link to post
Share on other sites

Just tested this on a site and it seems to works here fine. I'm running PW 2.3.0 with FormBuilder 0.2.1. 

Share this post


Link to post
Share on other sites

I just noticed I only answered apeisa in a personale message: I still don't know where the problem came from but after reinstalling FormBuilder everything works fine for me as well :). Thanks for notifying though!

Share this post


Link to post
Share on other sites

I tried this great module a few minutes ago - with ProCache disabled, it works as expected. With ProCache enabled, it doesn't: given one main domain and one  "campaign" domain, the browser displays the start page of the domain which was called first. I think it has to do with the .htaccess rules ProCache depends on.

Share this post


Link to post
Share on other sites

ProCache doesn't yet support multi-domain/multi-site, but this is definitely on the roadmap. 

  • Like 2

Share this post


Link to post
Share on other sites

Just wanted to chime in and mention what I've done.

I've been working on a new version of this module to support language page names. (mainly speaking only if LanguageSupportPageNames is installed)

- support Multilanguage 
- support for correct view Actions from admin
- correct urls within admin
- modified locaUrl() to work correctly, coming from LanguageSupportNames module
 
I hope you guys don't mind. 
 
I forked the project and comited current version. As you can see there's not much left from the original, but the basic concept is the same. This work was supported and sponsored partly by http://dreikon.de/ with whom I've been doing some PW support work lately. 
 
Since it's already some time ago since I made it (meanwhile tons of other work in my head) I just tested again locally with and without LanguageSupportPageNames installed and corrected a little issue.
 
I'd very appreciate if you guys help test this version. And any help or suggestions are welcome. It may not the best code ever written, especially since it's kinda complex I'd be very happy if more eyes take a look.
 
Ideally it would replace the current multisite module and be backward compatible.
 
Thanks
 
You can grab the module here:
  • Like 4

Share this post


Link to post
Share on other sites

Nice work Soma. I haven't yet tested, but have looked through the code and it seems solid to me. I don't yet have any instances where I'm using multi-site in production, but need to start doing so–very useful. Even more so extended like this. 

Share this post


Link to post
Share on other sites

Hi there,

I'm trying this Multisite module in combination with multilanguage page names, but seem to be facing a bug. I'll add some screenshots which will hopefully clarify things.

Little background on my installation:

  • PW version 2.3.7
  • Language support page names  0.0.8
  • Soma's multisite module version 0.0.2, with the configuration below:
www.msite.nl.frits
www.msite.de.frits

These domainnames are only active on my local development environment, so don't bother trying to browse them yourself :)

My pagetree is as follows:

multisite_pagetree.JPG

The contents tab of this page:


multisite_pageedit.JPG

And the settings tab:

multisite_pageedit_settings.JPG

Now when I browse to http://www.msite.nl.frits I get the default content of this page, as expected.

However: when I navigate to the German domain http://www.msite.de.frits, I'm suddenly redirected to this URL:

multisite_browser.JPG

It seems like the the module only looks at the main page title, instead of the page names configured under the settings tab. I've looked at the code but am not quite sure how to fix this. It looks like the redirect is not issued in the Multisite module, but somewhere outside.

Any help or insights would be much appreciated!

Share this post


Link to post
Share on other sites

Had a short talk with Soma on IRC.

To summarize and be complete: I thought of using the module to have 2 websites, each multilingual with their own domain for each language. I figured I could use the multilingual aliasses of each website to alternate the languages. Unfortunately it does not work that way.

I assumed this could look something like

  • www.firstwebsite.nl (pagename)
  1. www.firstwebsite.nl (alias)
  2. www.firstwebsite.de (alias)
  3. www.firstwebsite.en (alias)
  • www.secondwebsite.nl (pagename)
  1. www.secondwebsite.nl (alias)
  2. www.secondwebsite.de (alias)
  3. www.secondwebsite.en (alias)

Soma suggested to just use www.firstwebsite.nl/nl www.firstwebsite.nl/de www.firstwebsite.nl/en and the same for the other website.

I'll see if I can tweak the module to support my needs. If not then I will probably resort to fiddling with .htaccess. Unless someone has a bright idea on how to solve this ;-)

Share this post


Link to post
Share on other sites

I don't know on the multi-site module side (haven't yet used it). But in your case I'm not sure you necessarily need or want the LanguageSupportPageNames module. All you need to do is detect the language from the hostname in your head.inc or $config->prependTemplateFile. The fact that the hostnames select the language makes everything simpler. 

if($config->httpHost == 'www.website.nl') {
  $user->language = $languages->get('nl'); 
} if($config->httpHost == 'www.website.de') {
  $user->language = $languages->get('de'); 
} else {
  $user->language = $languages->get('en'); 
} 

Share this post


Link to post
Share on other sites

I haven't seen this addressed, so sorry if I missed it, but is it possible to have a a combination of multisite option #1, and option #2? That is, can I have, say, 4 sites in one db and 3 in another, all running off one /wire folder?

Share this post


Link to post
Share on other sites

It probably is possible. It's going to use whatever database is defined in your /site/config.php or /site-[n]/config.php file, so that's pretty much all there is in terms of defining what database is going to be used. 

Share this post


Link to post
Share on other sites

Using Soma's version of multisite (which works great) I stumbled upon weird issue. Using form builder I cannot display the f2nd language form while the standard language works fine. Cannot present a link, but the issue comes from a wrong iframe URL.

The german version is fine:

<iframe frameborder="0" id="FormBuilderViewport" allowtransparency="true" style="width: 100%; height: 682px;" src="http://sub.domain.ch/form-builder/is_kontaktformular/" scrolling="no"></iframe>

while the english version shows up like this:

<iframe frameborder="0" id="FormBuilderViewport" allowtransparency="true" style="width: 100%; height: 700px;" src="http://sub.domain.chis_kontaktformular/"></iframe>

so apparantly "/form-builder/" is missing in the iframe URL. I don't think it is a form builder issue (since multilang forms work usually), rather a problem with URL generation of multisite. I think the problem is here :

public function embed($formName, array $vars = null) {

		$out = "\n<!-- " . FormBuilderMain::RCD . " -->\n"; 
	
		if($formName instanceof FormBuilderForm) {
			$form = $formName; 
			$formName = $formName->name;
		} else {
			$form = $this->load($formName); 
			if($form) $formName = $form->name; 
				else $formName = '';
		}

		if($formName) {
			$page = $this->pages->get("template=" . FormBuilderMain::name); 
			$url = $page->httpUrl . $formName . '/' . $this->embedQuerystring($form, $vars); 
			$out .= str_replace('{url}', $url, FormBuilderMain::embedCode); 
		} else {
			$out .= $this->_('Form not found');
		}

		return $out; 
	}

I am not sure what goes wrong here. Either the selector for finding the form builder template (which I duplicated in the subsite's tree) or the generation of the URL because of the multilang situation. 

Any ideas?

Share this post


Link to post
Share on other sites

Is the form-builder page active in that language?

  • Like 2

Share this post


Link to post
Share on other sites

I went ahead and gave it a try... It looks like it's redirecting to the new root page correctly, but the admin directory becomes inaccessible. 

Share this post


Link to post
Share on other sites

I went ahead and gave it a try... It looks like it's redirecting to the new root page correctly, but the admin directory becomes inaccessible. 

No problems here with current stable release of PW. Do you use Soma's version? Works fine.

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