Jump to content

Search the Community

Showing results for tags 'Subdomain'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 13 results

  1. I'm trying to install Matomo on my host (world4you). For that purpose, I created a subdomain, a database and a folder in the root. In the subdomain settings I let it point to the created folder. However, the contents of the folder cannot be accessed in browser because it's redirecting to www So I have analytics.mydomain.tld and it's redirected to www.analytics.mydomain.tld I guess that's a .htaccess issue in the first place. But how do I amend the .htaccess-file of the site-root without affecting the main site? Here's I guess the relevant part of the .htaccess file # ----------------------------------------------------------------------------------------------- # 13. Optional domain redirects (O) # # Redirect domain.com to www.domain.com redirect (or www to domain.com redirect). # If using then uncomment either 13A or 13B, do NOT uncomment both of them or nothing will work. # ----------------------------------------------------------------------------------------------- # 13A. Redirect domain.com and *.domain.com to www.domain.com (do not combine with 13B): # ----------------------------------------------------------------------------------------------- # RewriteCond %{HTTP_HOST} !^www\. [NC] # RewriteCond %{SERVER_ADDR} != # RewriteCond %{SERVER_ADDR} !=::1 # RewriteRule ^ %{ENV:PROTO}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] # 13B. Redirect www.domain.com to domain.com (do not combine with 13A): # ----------------------------------------------------------------------------------------------- # RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC] # RewriteRule ^ %{ENV:PROTO}://%1%{REQUEST_URI} [R=301,L]
  2. Hi, I should install processwire on a subdomain. it is already installed on the main domain. Are there any techniques to handle the dual installation more organically?
  3. Hi, I'm looking at how I might achieve the following with Processwire: A low-bandwidth version of a website, on a subdomain (eg text.mydomain.com), where the content/database is exactly the same as the top level domain, but a new set of templates is used so the site is stripped back to just very simple CSS/low quality images. I'm looking and trying to work out what might be best — is it multi-site from the same database? Multi-instance? API? Any guidance or experience of a similar setup would be much appreciated.
  4. Hi, My client has a specific need where they need the website to be hosted in a subdirectory in the root domain; but need the admin panel to be accessible only via subdomain. They say this is for the security purpose. Frontend: https://example.com/app/ Backend: https://appadmin.example.com Anyway I can quickly achieve this? Thanks a lot.
  5. 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
  6. Summary: If I have a site sitting on a server called testing.com, then on the server change it to mycompany.com, do I have to modify any settings in ProcessWire? After building several processwire for clients, the one question that I haven't had is about moving a processwire site from an old (temporary) domain to a new domain. For instance, I typically setup development sites for clients and register a temporary domain (and lock with a password). For instance, thee client can go test.com and get all their content finalized, change wording, add news, swap out photos -- everything to make the site production read. Next, on my hosting account I can have testing.com renamed to theircompany.com - and change the nameservers. A simple question here. If I have a hosting company rename the account from testing.com to theircompany.com, change my nameservers whereas going to theircompany.com loads the production site, Is there anything I need to change in the processwire configuration or in the PW database? In the past, I've just manually copied the site, and fresh-installed PW, and imported the data. Seems like a lot of hassle. I have a second part question about updating the PW core, however, after consideration I'll post it as a new topic.
  7. I have a subdomain. Now i dont to use that subdoamin so i have deleted but if I open the subdomain it is redirecting to 404 page. Thank you in advance.
  8. Hi. I'm trying to figure out what might be the best approach when using PW for your CMS, but needing access custom tables. I know you can query your custom tables, so that's not my question here. What I'm trying to figure out is if I should separate an application from PW. Out of the box, the application I will be using has its' own tables and the app is built towards using those tables, so I don't want to rewrite the app to use PW, seems too much work. I do however want to use PW for the CMS and frontend where my users can add/update rows in those custom tables. Now the app itself can be connected from various devices on a handful of ports, so I'm expecting a high volume of requests to the app to a point where I'm seriously considering a dedicated server for this project. Would it be beneficial to create a whole subdomain just for the app and use PW to query the db? Or should I keep the 2 in the same db? Pros/Cons would be great here. Thanks!
  9. Hi all, I have problems to keep my session on different subdomains (including www). I've set the following config: $config->sessionCookieDomain = '.mydomain.net'; $config->sessionCookieSecure = false; But it doesn't work, I always loose the session when I switch between www.mydomain.net and example.mydomain.net. Could it be because both of them have a different SSL-Certificate? (https) Thanks for any help! Dennis
  10. Hi Everyone, I'm trying to figure out how to forward all subdomains to a single domain. For example, if the user goes to ... http://sharespost.com). I saw some similar posts about this but nothing concrete. Anyone have any thoughts? Any help is appreciated. Thanks.
  11. Hi there, I installed PW here: new.mydomain.com Then I'll switch to www.mydomain.com I think all I have to do is copy all the files from "new" to root, isn't it? (I mean: there's no need to transfer DB, right?)
  12. G'day everyone I'm new to ProcessWire - hoping someone could help me out?? I've installed ProcessWire in my root (public_html) directory & all is good - I really like this CMS. Very happy I stumbled across it! Thank you! This processwire site is accessible from my main domain (www.example.com) - No problem. However... I also own another domain name which I want to use for an entirely seperate website, but hosted on the same server account. Now, I've done this before with basic web pages with no hassles. But, with ProcessWire already installed - I'm having issues? In my cPanel admin area I create an Add-On Domain (www.secondwebsite.com). This creates a new folder in the root e.g. public_html/secondwebsite.com, and also creates the subdomain secondwebsite.example.com (which I'll deal with later). So, I place a Hello World index.html file within the new public_html/secondwebsite.com folder - This is to be the front page of my second website (entirely seperate from the ProcessWire site). When I type www.secondwebsite.com in my web browser, it is supposed to load that index.html file... Instead, I am greeted with a 403 Forbidden Error: Spewing. I did a bit of Googling to try and find a solution and found this thread which seems to have the answer, but I just can't figure out how to apply it to ProcessWire? I applied the fix they suggest in that thread by adding: To the start of the .htaccess file in my public_html folder. No luck. I tried placing it in different areas of the file, such as after the ReWriteEngine on line... Still no luck. Now, I've verified that it is the ProcessWire .htaccess file which is causing the issue, as I renamed the file, and I was instantly able to access my Add-On Domain from www.secondwebsite.com Could someone PLEASE help me out with this issue? I really don't have much experience with .htaccess files. If I can't resolve this it messes up my website plans for using ProcessWire Any help is greatly appreciated, thanks. Nick
  13. Hello guys, is there a way to manage some fakes subdomains like pages in PW? I mean: sub.domain.com => domain.com/folder Maybe via htaccess... Thanks
  • Create New...