[wp-hackers] Site Address in Posts Table
Greg at humhost.com
Fri Sep 3 15:47:47 UTC 2010
It's quite common in my practice to work with other people's existing
wordpress sites. I've seen this problem come up again and again. Yes I
can fix it with a DB query, no wordpress should not require an expert
who is comfortable with SQL to fix stupid mistakes like this.
The URL for the server should not be in the database table for posts.
Not only is this information redundant, having some posts set to one URL
and others set another causes data integrity problems which manifests
itself as broken websites.
The solution as was already suggested is to remove the URL from the
posts table and read it from a file.
On 09/03/2010 04:23 AM, wp-hackers-request at lists.automattic.com wrote:
> Send wp-hackers mailing list submissions to
> wp-hackers at lists.automattic.com
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> wp-hackers-request at lists.automattic.com
> You can reach the person managing the list at
> wp-hackers-owner at lists.automattic.com
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wp-hackers digest..."
> Today's Topics:
> 1. Re: Site Address during development (Mike Little)
> 2. Re: Site Address during development (Christian Gundersson)
> 3. Re: Site Address during development (Gavin Pearce)
> 4. Re: Site Address during development (Philip M. Hofer (Frumph))
> 5. Re: Site Address during development (Mike Little)
> 6. Re: Site Address during development (Gavin Pearce)
> 7. Re: Site Address during development (Bjorn Wijers)
> Message: 1
> Date: Fri, 3 Sep 2010 09:57:12 +0100
> From: Mike Little<wordpress at zed1.com>
> Subject: Re: [wp-hackers] Site Address during development
> To: wp-hackers at lists.automattic.com
> <AANLkTi=B4_82dgp75A80E+Y0KJEGHMh8abm-=ePMZ-J1 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> On 3 September 2010 09:52, ErisDS<erisds at gmail.com> wrote:
>> I guess what's kinda irritating about this, is the "why", rather than the
>> "how to solve".
>> It just doesn't make sense why absolute URLs are embedded everywhere.
> If you had followed this thread you would have already seen the answer:
> You *have* to have absolute URLs in RSS feeds and other non-browser
> situations, otherwise images, and especially podcasts would break, because
> the content is not being consumed in the context of the site and a browser.
More information about the wp-hackers