How to keep Admin panel on subdomain while frontend is to be on subdirectory?
Recently Browsing 0 members
No registered users viewing this page.
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.
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.
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.
By John W.
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.
By Dennis Spohr
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!