We have now changed the server within our webhost, since the new PHP 5 support, has clearer management capabilities and also provides better opportunities for the analysis of log files.
But what is all so after a server change? Updates from MySQL data are just the beginning.
All references must be changed and files relinked.
This is also an opportunity finally to make new structure, how it looks here at the blog the best. It will not be redirected to the web long, but remained directly in blogUrl.
But the so everything goes with WordPress 2 hours were up and down tasting of distress, which I will not just own the cleanest solution, but in any case, a functioning.
Sun and WordPress blog URL are set to this address, but using. Htaccess is forwarded to the other server. This, however, only documents for PHP and paths. Images are retrieved directly from here.
Why did I do all the work myself? 1 & 1, where the domain is, does not have PHP support and I can not therefore not be there to run the blog, but on a PHP enabled web space.
Currently, I'm still working on the solution, but if it is "ripe" for major tests, then I post it here.
Mfg BODY-Snatch
Update 1: I've now found a fairly simple way to solve this quite easily: # # on the server with htaccess RewriteEngine On derURL. RewriteBase / ^(.+( RewriteRule \ zip |. Rar | exe | tar | gz | jpg | gif | css | js)) $ http://wordpress.server/ $ 1 [L] # # No proxy to protect the Traffic RewriteRule (.*) http://wordpress.server/ $ 1 [P] # # Proxy (URL above are popular.) # #. Htaccess on the server with the WordPress installation RewriteEngine on RewriteCond% {REQUEST_FILENAME}-f RewriteCond% {REQUEST_FILENAME}-d RewriteRule (.*) index.php / $ 1 [L] That's it and you have yours. Htaccess in the wordpress directory provide even chmod 666 to 644, so that they can not be changed. In this example, you can now easily see that free domains, as my 1 & 1 can simply be laid over PHP web space, and the user no longer found where he is.
