[wp-hackers] Isn't it a problem for WP that it is so strictly attached to a specific domain?

[Nathaniel Taintor]

I'm not sure what you're referring to.

The only thing I can see that relates to WordPress being "attached to a
specific domain" involves rewrite rules, and even that isn't so much
"attached a specific domain" as it is "attached to a specific position in
relation to the domain root". That is, if you move your site from
domain1.com to domain2.com, you shouldn't experience any problems at all
from WP.  (You may have issues with content, such as img src's or internal
links being specified by absolute urls, but that has been discussed ad
nauseum over the years and there are plenty of ways of working around that
issue.)

Where you might have problems is moving from domain1.com to
domain2.com/site1 or vice versa, because that will necessitate rebuilding
your permalinks. But that's also a simple process and well-documented.

Can you explain what you see the problem as being?


Nathaniel Taintor, Designer/Developer
*Golden Apples Design*
http://goldenapplesdesign.com

@GoldenApples | 717.434.3226
goldenapplesdesign at gmail.com


On Mon, Feb 18, 2013 at 10:17 AM, Davit Barbakadze <jayarjo at gmail.com>wrote:

> Isn't it a problem for WordPress that it is so strictly attached to a
> specific domain?
>
> Why is this necessary anyway?
>
> Davit Barbakadze
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>