Search the Community

Showing results for tags 'multisite'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Found 19 results

  1. 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!
  2. Hi! 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.
  3. Hello, I am new to PW and learning this great tool for web development. I have already created a site for portfolio showcase using PW Same site templates will be used for different portfolio showcase with different sites / domain and different database. For all the sites front end design/display will be same. So, in future if I wan to modify display of sites, I have to edit template file [ i.e. /site/template/file.php ] for each domain, which is not a good solution. I want a solution where I will modify at single place and that will be reflected in every domain / site. Is there any way to achieve this ? Please guide
  4. Hello, i need help i dont know what happen but i get this error Its an multipage installation with one core and many languages. EN Version is ok but the DE version always error 500 also if i try to login to the backend. Exception: You do not have permission to execute this module - ProcessPageView (in /homepages/17/pathtosite/wire/core/Modules.php line 1225 Errorlog: 2016-11-26 11:13:37 guest http://de.mypage.com/?/ Error: Exception: You do not have permission to execute this module - ProcessPageView (in /homepages/17/pathtosite/wire/core/Modules.php line 1225) 2016-11-26 11:13:57 guest http://de.mypage.com/?/ Error: Exception: You do not have permission to execute this module - ProcessPageView (in /homepages/17/pathtosite/wire/core/Modules.php line 1225) #0 /homepages/17/pathtosite/wire/core/Modules.php(1130): ProcessWire\Modules->getModule('ProcessPageView') #1 /homepages/17/pathtosite/index.php(53): ProcessWire\Modules->get('ProcessPageView') #2 {main} 2016-11-26 11:14:34 guest http://de.mypage.com/?/ Error: Exception: You do not have permission to execute this module - ProcessPageView (in /homepages/17/pathtosite/wire/core/Modules.php line 1225) #0 /homepages/17/pathtosite/wire/core/Modules.php(1130): ProcessWire\Modules->getModule('ProcessPageView') #1 /homepages/17/pathtosite/index.php(53): ProcessWire\Modules->get('ProcessPageView') #2 {main} 2016-11-26 11:14:51 guest http://de.mypage.com/?/ Error: Exception: You do not have permission to execute this module - ProcessPageView (in /homepages/17/pathtosite/wire/core/Modules.php line 1225)
  5. I'm wondering if anyone else has attempted this before. I've setup a basic test multisite installation that effectively includes the master site and 3 others subsites using either the basic or intermediate template. I can't remember which and there might even be a mix of both among them, but I don't think that should cause an issue. What I want to achieve is a Home tab in the navigation menu on each of the subsites that links directly to the Home page of the master site. Is it possible to do that within the processwire admin or is it something that is going to have to be hardcoded into the template file. If the latter, do I go about that as I cannot see anything that appears to relate to the navigation in each of the site directories. i.e. Is it possible to add a menu item to the left of the subsite "Home" page now named About that is simply a link named "Home" that redirects to the Home page of the master website? Any thoughts would be greatly appreciated.
  6. Hello, I need to redirect the old paths after migration to a multisite PW installation. There are 3 domains and small differences between paths i.e. old path: domain-2/?text new path: domain-2/text or domain-2/new_text I try it via .htaccess (in the root direction) with an 301 redirect: redirect 301 domain/old_path domain/new_path -> generates an 500 server error What is wrong? How to do that?
  7. Hello, I am using Antti Peisa's Multisite module. For those people who are not familiar with it. Here is the link: http://modules.processwire.com/modules/multisite/. It works like this: It gets the current URL that visits the page via $config->httpHost and then redirects to a page who has the same name (e.g. get it via: $pages->get('/www.multi-site.com/')). The problem: $config->httpHost is locally something like "multi-site.local" and the redirection does not work because the ".com" url is hardcoded as page name. So I thought: Why not solve this problem by replacing the value of $config->httpHost in a module via: $this->wire->config->httpHost = str_replace('.local', '.com', wire('config')->httpHost); Is this a good way of doing this? And if yes: How can I say that my module loads first in the booting process? Are there any dangers with this approach? If so: any better ideas? I am not a great programmer Thank you!
  8. Hello, I'm about to suggest a CMF/CMS for a scalable project in my company and I really need your input here to get PW on board. The idea is simple - Build a main website - www.acme.com - And than build independent but related websites using the subdomains - product.acme.com / something.acme.com - Each subdomain will have their own website and staff team. What do I need? - All the websites should be able to have their own backend. The reason for that is because the staff from product.acme.com will be different from acme.com. So, I don't want a staff from product.acme.com to be able to "see" the acme.com backend. - To be able to setup independent pages design/features for each sub-domain. ===== It's something like google.com and their sub-domains. You have adwrods.google.com / maps.google.com / translator.google.com and so on. They keep their main brand visible - google.com - and add their different products from subdomains. In my case, the subdomains will only host another simple website. How would you approach this project? Please let me know if you need more clarification. Best regards, Zilli
  9. I am using the Multisite.module to run several (similar/related) websites off a single PW-site and database. Adding new sites was as simple as adding the domain to the config box, and a top level page of the same name. However, since an upgrade of PW, I now also have to update my site/config.php file with each extra domain, i.e. $config->httpHosts = array( 'mydomain.com', // our primary hostname 'related.mydomain.com', // related website ); Otherwise the site will throw a 404 page not found. Leaving a blank httpHosts will allow all hostnames, but causes a warning in the back-end Unrecognized HTTP host:'mydomain.com' - Please update your $config->httpHosts setting in /site/config.php Can anyone advise how best to update Multisite.module?
  10. perhaps this is the wrong subforum, perhaps there are better waays to do this, but I wanted to share some thoughts regarding multi sites together with multiple robots.txt If you are running multiple sites with one PW setup you can't place multiple robots.txt files into your root. As long as all robots.txt files are identical there is no problem with it. You can stop reading right here. In my robots.txt I wanted to include a link to the current sitemap, e.g. Sitemap: http://www.domain.com/sitemap.xml I put each robots.txt into the "site-" directories. Search engines expect the robots.txt file directly in the root so I added some lines to my htaccess file (for each domain you have to do this) # domain 1 RewriteCond %{REQUEST_URI} /robots\.txt RewriteCond %{HTTP_HOST} www\.domain\. [NC] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /site-domain/robots.txt [L] # domain 2 RewriteCond %{REQUEST_URI} /robots\.txt RewriteCond %{HTTP_HOST} www\.domain\-2\. [NC] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /site-domain-2/robots.txt [L] Another possible approach: create a PW page within each site
  11. Hello All, So I've launched my first PW site: http://www.neighborhoodsewerdrain.com - yea! Next challenge: We have an 11 county service area in south east Michigan. My boss would like the site to function in such a way as to "localize" the site depending on where the user is located. So, if the user clicked on a Google AdWords ad targeted at Macomb County, the URL would be "www.neighborhoodsewerdrain.com/macomb/". From there, I'd like to pull in dynamic content specific to that region, like a local phone number, the words "Macomb County" wherever I want to drop them in the content (most likely using Hanna Code or code in the template). Further, once the user enters through the above sample URL, I'd like to prepend "/macomb/" to the root domain as the user visits other pages, which will keep the content localized. This would be ideal so as not to have to manage 11 different versions of each page. I've begun to experiment with URL Segments and PHP switch statements. I'm sure it's going to get a bit more complicated than that. So, if anyone can point me in the right direction with suggestions on how to pull this off, it would be most appreciated Thanks!
  12. This question follows on from the discussion that starts here. A screenshot of the page tree is attached. On the subsite, the content of About displays OK, but all the subpages of About only display the page title. Template code is: <?php /** * NPL Page template * */ if(count($page->includePage)>0) $page = $page->includePage; $outMain = '<h1>'.$page->title.'</h1>'; $outMain .= $page->body; include("./npl-main.inc.php");
  13. My organization is looking at moving our various websites to a CMS. As we have probably 20 - 30 sites, I want to do a multisite setup, using the multisite module, so that we don't need to maintain so many duplicate user accounts for our content editors. I'm wondering how I'm supposed to hook into $page->rootParent to get it to return its appropriate child. I'm thinking I'll setup the page tree so that Home is just a dummy page, and all my real sites' homepages will be its direct children. That way I think I should be able to make the change to the rootParent method universal without having issues. How could I accomplish this? Am I making some horrible mistake which I have been unable to percieve thus far? Thanks.
  14. Hi, I'm trying to set up a multisite with following specifications: 2 different URLs I have to reach the backend via the two URL's (eg. http://example-firstsite.com/processwire/ and http://example-secondsite.com/processwire/) so that i can create different user / editor roles witch only get "their content" I want to use the nearly same template-files on both sites I want to use only one core I want to share some content between the sites I want to have a "child-page based database for persons" witch I can query and use on both sites with it's own url I tried to use apeisa Plugin Multisite but had to recognize that it´s not possible to use it without having a "master-site" Can you give me any advices how to set PocessWire up to comply with the requirements? Many greets, Jens alias DV-JF.
  15. I'm getting to know Processwire relatively well, and now I have a nice big challenge ahead of me and I'm trying to lay out my plan of attack. One of my peers reckons I should use WordPress Multisite, which I know is definitely a viable option, but I would much prefer to use Processwire. I know it's not a question of "Is it possible?" It definitely is. It's just a question of "What's the better approach?" Here's the situation: I'm setting up a service that will build site pages for multiple clients (aka baby sites) but all under one domain (aka mothership). The baby sites will use folders, not subdomains. Most of the baby sites will be one page only, but some may stretch to three pages *gasp*. And of course each baby site will have a completely unique look - so there'll be as many templates as there are babies and potentially more templates than babies. The mothership will be its own site with its own pages discussing how to become a baby and the benefits of being a baby. So it will look something like this: mothership dot com - with about 4 of its own pages mothership dot com/baby1 mothership dot com/baby2 and so on up to about baby1000 (potentially) Now here's my thought process. NON NEGOTIABLE - Use Processwire NEGOTIABLE: 1. One PW site, each baby is just its own page with child pages where necessary 2. One PW core install, each baby is a separate PW site running from the same core wire. PROS and CONS of the two alternatives as I see them: Alternative 1: PROS - Really easy to install and just create the babies as pages on the main site tree. Easy to update core and modules/plugins CONS - Will it become difficult to maintain as the babies approach the thousands? Will it scale or will it crash? Will it become a future model of the dangers of putting all your eggs (or babies) in one basket? Alternative 2: PROS - Would be nice and easy to maintain from one core, since I only have to update just the one wire folder. Might scale easier since they're different sites, each with just a few pages. Any other advantages? CONS - Don't even know if this is doable? - Would I need to update each site's modules separately? Annoying Your thoughts and recommendations are much appreciated by the mothership and the many babies, and by me of course
  16. I've been testing out the multisite feature of processwire installing via option 1 in the docs. I managed to get everything working by following the first option which requires installing a new version of PW and copying the files over to a site-mysite directory. I'm now testing out the second option which just needs the site files copies to a site- directory and importing the DB from another installation using PhpMyAdmin. The installation worked fine but when I try to login to the admin the username and password I used from my clone site are not recognised. I thought the password would pull over from the SQL database. I'm sure this is something really simple but I'm scratching my head at the moment. Any ideas?
  17. I noticed there is a file named index.config.php in /wire which is the "ProcessWire multi-domain configuration file" and I'm wondering if this is for multiple PW sites similar to WP Multisite or EE MSM or am I confusing it with Multi Environment setups. For example if I wanted to have a local, dev, staging, live/production multi environment setup would this be the file to use? Where all the domains, paths, db settings would most likely different from enviro to enviro? It looks like this is in fact for setting up multi-environments now that I read and understand what's taking place. The fact that it's called mulit domain is throwing me off a little, however and why I wanted to double check I guess. Is there anything to worry about with these types of setups in regards to paths or does PW handle all that for us and we just need to worry about setting up things per the instructions in the file? Any gotchas in other words?
  18. Hi guys, I have been playing around with multisite recently and wondered - what would be the best way to share some template logic between multisite instances? I have an upcoming project where two different sites would have different users and setups etc but they need to share some basic similarities in look and functionality. I was thinking of setting up the sites as separate sites under multisite and then finding a way of sharing something such as a 'main.php' file that each template calls. I would also like to share a 'base.css' file between the sites as well. I want to do things this way because they want the potential to be able to expand into more sites over time - up to 5 or so. What would be the best way of doing this? Thanks in advance.
  19. Hi Guys, I have read through other topics on using PW for multisite setups and am a bit none the wiser unfortunately. Let me explain my scenario: I have a potential client project whereby they want to have 3 websites all as separate websites in terms of: content look & feel domain names Users However, for me to setup up the websites for them it makes no sense for me to be managing 3 separate hosting accounts and them to be paying for all of that. Also, 1 of their websites will be a primary site with a few thousand visitors per month, but the 2 more secondary websites will only have a couple of hundred visitors. Perfect for a multisite install to my mind which wouldn't tax server resources too much. This to me seemed a perfect opportunity to setup a multisite under one hosting environment whereby domains are mapped to subdirectories or whatever setup I would need. My problem is that I have no idea as to how I go about setting all of this up in PW. I have done this before with WordPress using the domain mapping plugin under a multisite install. All without dealing with symlinks or much code at all. However, I would really like to use PW for this as long as it's not too complex. With PW I can deliver a client user experience in the admin area that is much more streamlined for their particular use case.