Jump to content

Search the Community

Showing results for tags 'multi-site'.



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

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 12 results

  1. Hello PW community, I hope my post fits correctly in this forum category. Great to be here. Great to have found my new favorite CMS and an awesome community! I learned a lot from you guys by lurking on the forums and I hope can help someone else in the near future. I could need some advice about a very specific subdomain setup with a single PW install. A multi-language multi-site setup 1x top-level domain but with subdomains for country specific site versions Some subdomains have the same language (different country), others differ Current setup using apeisa's Multisite module In Page Tree Domain Country Language / www.domain.com International site english /en.domain.com/ en.domain.com United Kingdom english /de.domain.com/ de.domain.com Germany german /at.domain.com/ at.domain.com Austria german /ch.domain.com/ ch.domain.com Switzerland german /fr.domain.com/ fr.domain.com France french ... I guess the name for something like that is "Geo-Targeted Subdomain Approach". I first wanted to do a folder-based language approach but the requirements have changed - thanks to the SEO guys *yay* :-/. In advance Since the project must be finished during the next few weeks, if anyone of you PW professionals is available short term, I would be interested in talking to you to find a solid solution to make this work. The site's content will grow soon and I'm concerned how the client will be able to manage all of his different country sites (subdomains). For example my current challenges are with managing lots of content in this environment, PageListSelect, sitemap.xml generation and more. The site is working but things are starting to get complicated and some functionality undesirable. I guess mostly of how the subdomains are set up with the Multiside Module. My question I don't know how I can efficiently marry the multi-language features of PW and this multi-site setup with subdomains. Also there may be other solutions for the subdomain setup beside the Multiside module. If any of you has an idea, did something similar or could give me some pointers in how you would approach a setup like this - that would be so awesome! The Challenge and options in how to prevent a content management Massacre Managing multi-language content in a multi-site environment, preferable with single pages and not duplicate content Can it be done with LanguageSupportPageNames of PW 2.3.1/2.3.2 dev branch? I'm still not sure If I should be using the dev branch for a live production site. Current setup I have already set this up and it's working fine using apeisa's Multisite module - which was a real life saver, since the site had to go live very quickly in a light/base version. The site content Company with a single product and pages like support (can be many pages), faq, forms etc in each country All countries (subdomains) describe the same content, but text and images can be different on subdomains in a different or same language All subdomains/sites have many pages in common but not every page does exist in every country. Most content is currently duplicated on all domains and this creates a mess as the site grows obviously. Have not found an efficient solution for a multi-site/multi-language page/field setup No PW language support is currently in use I already thought a lot about how to reduce complexity of my setup, created some working snippets but encountered some problems. Was thinking about letting the content live somewhere hidden on the site, creating my own function or by using something like this and pulling everything in with a nice and easy configuration (field to select a country etc..), which with my PHP/PW knowledge sounds insane to be build by myself. I have more information, but I didn't want to spam this post - hrm *cough*, as I've done already. Phew, sorry for the long post. Any feedback is much appreciated. Thank you so much in advance and thanks for reading this. Regards //symb
  2. Hi there, I'm trying to have a multi-site (multiple databases) setup on a IIS (Microsoft) server. I know that IIS is not officially supported by ProcessWire but customer is insisting on IIS. I get an 500 Error when trying to access the sub-domain/other processwire site. Did somebody do this before or is it not possible at all to have a multi-site setup on IIS? Thanks
  3. Hi Everyone, I was playing around with the ProcessWire command-line script sitemap.sh (https://processwire.com/docs/front-end/include/) I currently have a multi-site setup (with separate databases). -> site -> site-other The sitemap works but it shows only the pages from the default site directory. How can I get the sitemap of the site-other directory? Here is my working code that prints the sitemap of 'site': #!/usr/bin/php <?php namespace ProcessWire; include("index.php"); // bootstrap ProcessWire function listPage($page, $level = 0) { echo str_repeat(" ", $level) . $page->title . "\n"; foreach($page->children as $child) { listPage($child, $level+1); } } listPage($pages->get("/")); // start at homepage I tried including index.config.php instead of index.php but that didn't help...
  4. Using ProcessWire's in-built multi-site support (option #1 here), is it possible to bootstrap the various sites? To bootstrap ProcessWire, the only requirement is to include /path/to/processwire/index.php/. In option #1, there is only one index.php. So, including index.php defaults to bootstrapping the main site (i.e. the site at /site/. Is it possible to bootstrap the other sites, i.e. site-dogs, site-cats, site-birds, etc? I've searched the forums but nothing relevant comes up. Thanks.
  5. Hi everyone, I am using ProcessWire to run a multi-site environment using the Multisite module by Soma. It's working great with one small caveat. It always defaults to the English version of the site. So when you access the base url (somedomain.com) it always redirects to somedomain.com/en/. In my particular case I need it to go to the Germany version somedomain.com/de/. Some things I've tried: I've tried fiddling around with the AutoDetectLanguage module to have a user redirected based on the detected browser language - didn't work. I've also tried messing with a module that changes what the default homepage is (smth like DefaultHomepage I believe), but that also had no affect. I used the Redirect module to have the root ('/') redirected to specific language URL ('/de/) - also didn't work My guess is that it has something to do with the default language in the setup which is set to english, but I am not sure. Has anyone else come accross this issue? Thanks in advance.
  6. Hi Folks, We have a multi-site #1, multiple sites, multiple databases platform in development/concept at the moment. A company can sign up, register, and PW then creates a db, copies over a site folder with /wire symlink. All seems to work well, after sign up they can then enter into their subdomain site. ( Because of this dirty hack below that inserts the new subdomain into PW's hostSiteConfig array. Without this, the subdomain is not correctly registered as a PW site & instance I think). Does anyone know how to dynamically add an entry into the index.config.php file ? Knowing the little I have learnt so far about PW, Ryan has probably left us a really smart way to do it, but I haven't figured it out or found it yet. I have done a dirty hack on it, which I'm not very happy or proud off. Anybody know of a better way around the problem ? ... below is more or else the code I am using in the pilot version. // some error traps taken out for brevity on the booleans below... $hostsArray = ProcessWireHostSiteConfig(); // $sitename normally populated from the customers signup/registration // hard coded here for this example... $sitename ='somesubdomain'; $a = $sitename . '.' . 'localhost:8020'; // machine name, port & protocol normally comes from $config, hard coded for example. $b = 'site-' . $sitename . '/site'; $newSite = array($a => $b); $hostsArray = array_merge($hostsArray, $newSite); // very dirty hack starting.... // creating a string copy of the array used in // index.config.php $newString=''; foreach($hostsArray as $key => $value) { $newString .= "'" . $key . "' => '" . $value . "', "; } $newString = "return array(" . $newString . ');}'; // dirty hack getting worse :-( $newConfigIndex = file_get_contents($config->paths->root . 'index.config.php'); $startpos = strpos($newConfigIndex, 'return array('); // quality coders starting to feel sick at this point i suspect... sorry! ;-( $newConfigIndex = substr_replace($newConfigIndex, $newString, $startpos); $boolConfigIndex = file_put_contents($config->paths->root . 'index.config.php', $newConfigIndex); // crikey! did he really just do that !!!!!!
  7. Having a problem with a basic multi-site instance. The multi-sites are dynamically created and run as sub-domains and all is ok with them. They are created during a sign up process by end users. During the sign up process - once the new site & db has been created, I had planned to load the new site instance and add a new user to it, using code similar to this.. $newSiteInstance = new ProcessWire($path, $newSiteUrl); $u = $newSiteInstance->users->add($sitename); $u->pass = $pass; $u->email = $email; $u->addRole('content-viewer'); $x = $newSiteInstance->users->save($u); This won't work in the registration script. It throws an error ... "SQLSTATE[42S02]: Base table or view not found". However, if I halt the script, load the new site incognito/other browser, then continue the script, all works perfectly. So $newSiteInstance = new ProcessWire($path, $newSiteUrl); doesn't seem to work for me unless a site has already been loaded in a browser or instantiated somehow. I am missing something here ? Does a site need to be bootstrapped before new instance will work on it ? Sorry, pretty new to this php/PW arena. Having fun though Any ideas folks ?
  8. I'm having trouble getting a multi-site installation (I'll call them "site1" and "site2") working on a shared cPanel host. The installation was working on my local hosting environment with two virtualhosts pointed at the same folder, allowing me to access both sites. On the cPanel server I'm wanting to use subdomains for both sites: site1.mydomain.com and site2.mydomain.com So in my cPanel hosting I have site1.mydomain.com as the primary domain for the account, and I have added site2.mydomain.com as a cPanel domain Alias (I believe this was called a "Parked Domain" in previous versions of cPanel). Before I edit index.config.php to perform the redirect to site2 I am able to see site1 at both site1.mydomain.com and site2.mydomain.com. But after I edit index.config.php to redirect I get: Maybe someone has experience with setting up a multi-site installation on cPanel. Is adding the domain for site2 as an alias/parked domain the right move? Something else I need to configure in cPanel?
  9. Hi there, I'm trying to set up different instances of our website so I thought I'd try it out locally first before deploying out to the real world. I'm interested in a multi-site/independent DB setup so I'm following the instructions (Step1 Alternative) in https://processwire.com/api/modules/multi-site-support/ The steps I've taken are : 1) I've copied my /site folder to /site-dev. 2) Modified index.config.php and moved it to the webroot 3) Modified config.php in site-dev and changed the DB credentials. I thought this was all the steps I needed to take but it didn't work. I've also added an entry in /private/etc/hosts for dev.localhost to point to 127.0.0.1 Is there something else I have overlooked? Thanks in advance! ------------------ index.config.php function ProcessWireHostSiteConfig() { return array( /* * Some Examples (you should remove/replace them if used). * Just note that the values must begin with 'site-'. * */ 'dev.localhost' => 'site-dev', /* * Default for all others (typically /site/) * */ '*' => 'site', ); } config.php $config->dbHost = 'localhost'; $config->dbName = 'SSS-Live';
  10. Hi, wow, this is weird: I am running two sites with one ProcessWire installation. Both are using VersionControl module. I moved both sites to another webserver right after installing VersionControl. On site #1 ...sometimes (!) file upload is not possible (the pink status bar gets stuck at 100 %) already uploaded files (before moving to the new server) cannot be deleted file descriptions cannot be changed no error messages are given, not even in debug mode While on site #2 ...everything's fine: uploading, deleting, changing the description... I read Douglas' post on a glitch in dev 2.5.19, but I'm using the regular 2.5(.0). nghi's post on a similar problem describes pretty much what I'm experiencing here, but if there was something wrong in the suhosin.ini, site #2 would encounter the very same problem. If I use VersionControl to set the file field back to an earlier version where the file was not uploaded yet, the file disappears and is deleted from /assets/file/[page-id]/. Same vice-versa when setting to a version before a file was deleted: It is recreated on the page and in the filesystem. Permissions are -rw-rw-rw- for all files. Any ideas? Sarah
  11. I'm developing relatively big site with a number of weakly connected web-services. By "weakly connected" I mean that they share same users and some common catalog but the rest (and bigger part) is not shared (service-specific catalogs, languages, etc). As site becomes too big and complicated I think to move these weakly connected web-services to their own sites, e.g. one PW core but several sites with their own dbs. Users as well as shared catalog remain at "main" site, being maintainable via PW admin. Before this move I'd like to consult with you guys. Specifically - would this code work at "web-service" sites? $temp = $wire; // temporary save "current site $wire" include("../../../site-main/index.php"); // bootstrap PW main domain $wire. Main domain and Service domain sites are in one directory, ../../../ path prefix used to navigate from current templates directory to common parent folder of all sites. $mainWire = $wire; // set variable to be used for access/manipulations at main site $wire = $temp; // set $wire back to "current site $wire" $user1 = $mainWire->users->get('email=email@example.com')->first(); // returns User instance from main site / main domain db $user2 = $wire->users->get('email=email@example.com')->first(); // returns User instance from current site / current domain db I am aware of http://modules.processwire.com/modules/service-pages/ but due to security&performance reasons I think that if "hardcode" above works then it should be a better choice. P.S. wire/index.config.php function ProcessWireHostSiteConfig() { return array( 'maindomain.com' => 'site-main', 'www.maindomain.com' => 'site-main', 'service1.com' => 'site-service1', 'www.service1.com' => 'site-service1', 'service2.com' => 'site-service2', 'www.service2.com' => 'site-service2' // etc other services ); }
  12. Hi, I have a project rebuilding a company website that does not have any CMS managing it at the moment. There is also the need for a separate site they refer to as an 'intranet' but it is more like a company resources website which is accessed by multiple interstate offices and also by sales staff on the move. This site contains files and info they would consider sensitive information. I am interested in using the multi-site feature of processwire to share some files across both sites. The resources website will have user login access, does anyone have any advice on additional security to protect the more sensitive company files? I have just started looking into VPN hosting for example, would this be necessary? Can I still use multi-site processwire if the company website does not require the VPN?
×
×
  • Create New...