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 is only 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 try of needs, 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 for PHP documents and trails. Images can be accessed directly from here.
Why am I doing all the work myself? 1 & 1, where the domain is located, has no PHP support and I will not be there, not the blog running, but on a PHP enabled web space.
Currently, I'm still reworking the solution, but if it is "ripe" for major tests, then I post it here.
Mfg. Body-snatcher
Update 1: I've now found a fairly easy way to solve this quite easily: # # htaccess file on the server with derURL RewriteEngine On. 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 are popular on top.) 1The's it and you have yours. Htaccess in the Wordpress directory or make chmod 666 on 644, so that they can not be changed. In this example, you can now easily see that free domains, as can my 1 & 1, can be easily placed over PHP web space, and the user no longer found where he is.