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 evaluation of log files.
But what is all so after a server change? Updates from MySQL data is only the beginning.
All references must be altered and files relinked.
This is also an opportunity finally to make new structure, how it looks here on the blog the best. It will not be redirected to the web long, but still directly in the blogUrl.
But so that 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, but only for documents and PHP paths. Images are accessed 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 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 large scale testing, then I post it here.
Mfg. BODY-Snatch
Update 1:
I've now found a fairly simple way to solve this quite simple: # # on the server with htaccess RewriteEngine On derURL.
RewriteBase /
^(.+( RewriteRule \ zip |. Rar | exe | tar | gz | gif | jpg | css | js)) $ http://wordpress.server/ $ 1 [L]
# # No proxy to protect the traffic
RewriteRule (.*) http://wordpress.server/ $ 1 [P]
# # Proxy (URL above, are popular.) 1The's it and you have yours. Htaccess in the wordpress directory still make chmod 666 on 644, so that they can not be changed.
In this example, you can now easily see that free domains, as my can of 1 & 1, can simply be laid over PHP web space, and the user no longer found where he actually is.
