Recently Browsing 0 members
No registered users viewing this page.
By Guy Verville
I know it is possible to have a different domain name for each language of a site. For exemple:
monsite.com (for French) mysite.com (for English) I know also that we can have several sites in one installation with the help of Soma's Multisite module.
I have a company who has four independent sites (four different companies under a same umbrella). The new design and structure of those sites will be practically identical. There will be different administrators for each site, but a lot of data will be shared, so using Soma's module seems to be a good idea. The problem is that those 4 sites have different names for the French and English version.
compagnieUn.com (for French) companyOne.com (for English) compagnieDeux.com (for French) companyTwo.com (for English) etc. Will we shoot ourselves in our feet to develop with just one installation? Would it be preferable to make those sites able to talk to each other instead?
Your input would be very much welcome!
By Jimmie Bragdon
Wondering if anyone can help me get past a sticking point.
I'm setting up a Processwire instance in a multiple site setup (using Soma's multisite) to run several related websites. I am getting stuck on the tagging system that I am using (adapted from a standalone PW site I'm running). I have the tags themselves set up as Pages, and the Tags field on the related pages is and ASMselect field that populates based on the pages underneath /tags/ in the tree. This system works fine on the standalone site.
Where I am running into issues, is with trying to use them with the multisite setup. Specifically, choosing the proper subset of pages for tags on the ASMselect input tab. I want to choose only the tag pages for the site in question.
My tree is laid out like this:
So far, the best I've been able to do is to use 'parent.has_parent=/tags/' in the Custom Find or Selector String portion of the Selectable Pages section of the input. This gives me the options of choosing tagA, tagB, or tagC on a page under site1.com. What I'd like to find is a selector that allows me to only see tagA, tagB as options from a page under site1.com and only tagC on a page under site2.com.
Elsewhere in my php templates, I'm using $page->rootParent->title to set the proper scope and URLs for things, but I have not found a way to get that to work in this field input setup. I am trying to avoid creating specific fields and templates for each site, as unified templates were part of the purpose of going with a multisite install.
Thanks in advance for any ideas.
Just a quick question, when using the multisite module is there anything different that needs to be done in order to setup HTTPS for each of the domains its serving?
Would a single SSL certificate for the main domain be enough to cover the others aswell or would you need multiple ceritficates one for each domain the mutlisite setup uses?
I have a question about Multiple Site implementation, and how to possible "share" modules between them.
First, required reading: https://processwire.com/api/modules/multi-site-support/ I'm dealing with Option #1.
The way this works is that in the root directory of a site, there is an index.config.php file that denotes what domain is mapped to which site-*/ directory.
The project I am working on has three site-*/ directories, each with their own site-*/modules/ directory.
What has happened is that a lot of the modules from site to site are the same.
I was wondering if there was any way to "share" modules between sites in the Multiple Site setup, via symlink or alias, or potentially if there was some roadmapped feature that @ryan has planned to solve this issue.
Either way, any help/pointers would be appreciated!
I've been working over a number of sites into processwire, but I have come across a strange bug I cannot wrap my head around.
I'm using method #1. Single wire directory, multiple site- directories with index.config.php and config.php set up properly.
I've had no problem setting domains in the configs up until this point. www and root domains are loading perfectly. However I tried to add a subdomain value 'new.domain.com' and I have put the bits in all the right spots. I get a 500 Internal Server Error.
If I change the subdomain to something else, same deal. Only domain.tdl and www.domain.tdl entries are working.
Any thoughts? I'm using the latest stable 3.X branch.