|
I'm migrating a bunch of Wordpress instances to a Wordpress application configured for multisite. So I have a website configured that points, say, wpmu.mydomain.com to ~/webapps/wpmuhq I'm using the Multidomain plugin, to point myfirstblog.com to mfb.wpmu.mydomain.com, blog2.com to b2.wpmu.mydomain.com etc. When I use the control panel to add a website that points myfirstblog.com to the wpmuhq app, I find that the Webfaction script automatically modifies the wp_options table for the wpmu app, to set siteurl and home to http://myfirstblog.com/ I understand why that would happen - if you're setting up a single WP domain, that's exactly what WP would require. But it messes up for a multisite: wpmu.mydomain.com/wp-admin is redirected to myfirstblog.com/wp-admin - not what I want. I can work around it, by resetting host and siteurl to http://wpmu.mydomain.com/ in wp_options. But: is there a way to set up custom domains with the WF control panel that doesn't require this workaround? asked 24 Jun '13, 09:46 cesnn |
|
If you want to avoid the automatic WP configuration that our control panel does, then you can either:
If you use either of the above approaches to serve your WP site, then our control panel won't do the WordPress-specific stuff that it normally does (i.e., automatic configuration of your site URL in WP options). Hope that helps! answered 24 Jun '13, 10:13 seanf Thanks, Sean. Any downsides from the approach I'm taking - e.g. that at some later time, a WF script would do something that tries to be helpful but breaks my workaround?
(24 Jun '13, 10:29)
cesnn
Nope, no downsides that I can foresee. This approach essentially turns your WordPress app into a generic static/cgi/php app, so there would be no special tweaks made by the control panel when it creates the web server config for that app.
(24 Jun '13, 10:44)
seanf
|
