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

Has anyone had any issues using this module with ProcessWire 2.4? Would it be smart for me to steer clear of it for the time being? :)

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

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 MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • 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-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 horst
      Croppable Image 3
      for PW 3.0.20+
      Module Version 1.2.0
      Sponsored by http://dreikon.de/, many thanks Timo & Niko!
      You can get it in the modules directory!
      Please refer to the readme on github for instructions.
       
      - + - + - + - + - + - + - + - + - + - NEWS - 2020/03/19 - + - + - + - + - + - + - + - + - + - 
      There is a new Version in the pipe, that supports WebP too: 
       
      - + - + - + - + - + - + - + - + - + - NEWS - 2020/03/19 - + - + - + - + - + - + - + - + - + - 
       
       
      -------------------------------------------------------------------------
       
      Updating from prior versions:
       
      Updating from Croppable Image 3 with versions prior to 1.1.7, please do this as a one time step:
      In the PW Admin, go to side -> modules -> new, use "install via ClassName" and use CroppableImage3 for the Module Class Name. This will update your existing CroppableImage3 module sub directory, even if it is called a new install. After that, the module will be recogniced by the PW updater module, what makes it a lot easier on further updates.
      -------------------------------------------------------------------------
       
      For updating from the legacy Thumbnail / CropImage to CroppableImage3 read on here.
       
      -------------------------------------------------------------------------
       
×
×
  • Create New...