[wp-hackers] Site Address during development

[Gavin Pearce]

> Now why add the extra overhead when it doesn't work and can't be
retrofitted?

I'm not so interested in the plugin approach, but would like to point
out that any approach could be retrofitted if need-be.

That said - as most problems occur from test/dev -> live, for sites
already complete one would assume that they are live, and domains less
likely to change.

G

-----Original Message-----
From: wp-hackers-bounces at lists.automattic.com
[mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Rich
Pedley
Sent: 03 September 2010 14:14
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] Site Address during development

On 03/09/2010 14:03, Gavin Pearce wrote:
>> What is being proposed is to enforce the calculation of the absolute
> URL on every single WordPress installation feed (and any other way the
> content may be accessed out of context of the web), to solve a problem
> that manifests
>> itself *at the point someone moves a site to a different domain*.
>
>> This 'solution' is 'fixing' a problem that doesn't exist.
>
> I fully see your point Mike, and it's a good one - I do though feel
it's
> more adapting the code to prevent possible problems - rather than a
> problem that doesn't exist as such.
>
> Your choice of words makes it sound like it's adding overhead - when
> really performance wise it would be the most nominal of differences.
>
> I mean ... if the core committers can force through code that changes
> "Wordpress" to "WordPress" (definitely not a major worry for
*anyone*),
> I can't see how this is any different? A small use case yes - but it's
> still solving a problem that some users do encounter, albeit not many.

The 'solution' offered (ie the plugin) doesn't retrofit. So in order 
for it to be of any use you would have to literally update every 
single page/post on your site. So as a solution it is of no use for 
any existing users out there.

To make it work for old posts/pages you would have to run a db 
query... oh wait they have to do that when they move WordPress as it is!

Now why add the extra overhead when it doesn't work and can't be 
retrofitted?

Rich
_______________________________________________
wp-hackers mailing list
wp-hackers at lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-hackers