[wp-trac] [WordPress Trac] #17048: URLs delivered to the browser should be root-relative

[WordPress Trac]

#17048: URLs delivered to the browser should be root-relative
-----------------------------+-----------------------
 Reporter:  dmole            |       Owner:  edwardw
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:
Component:  General          |     Version:  3.1
 Severity:  normal           |  Resolution:
 Keywords:  close            |
-----------------------------+-----------------------
Changes (by dd32):

 * keywords:   => close
 * type:  defect (bug) => feature request


Comment:

 >  http://lists.automattic.com/pipermail/wp-hackers/ seems to be the
 official yet external log

 Correct, That's the official (and not really external - it's just there's
 never been enough time and a compelling reason to set up the lists on the
 WordPress.org servers) location for such discussions.

 I'm not going to say it's a waste of your time continueing the patch, But
 I will say that since it's a design choice, Commitors are not likely to
 want to touch this, as such, any patch is simply going to go stale. You'd
 be far better off implementing this as a plugin which those interested can
 use, which would be more likely to be future compatible (I realise that
 determining where the url is being used would be hard, therefor, you'd
 have to just do it root-relative in the locations you *knew* 100% it'd be
 ok).

 One example for reasons a absolute url is easier, is when moving the site
 to another domain, You can simply replace all the site url's. With this
 solution, You can't reliably move it between directories, moving between
 hosts is fine, just as long as all paths end up the same. You'd also have
 to investigate Exports/Imports, as that would be affected too.

 Long story short, to me, It's not a problem that needs fixing, In the
 sense, that there are other solutions available already which fill the
 needs mentioned in this ticket. the output buffering items mentioned above
 are one method, my favourite method is to dynamically define
 WP_SITEURL/WP_HOME, or filter the siteurl option, or filter the
 site_url()/admin_url()/includes_url()/home_url() returns to respect the
 current hostname, etc.. there's always a method which suits the
 site/environment in question.

 Adding the close keyword again, to signify/track, that multiple developers
 have suggested it be closed, removing it doesn't change that decision.
 Also, It's a feature request to use root-relative links, as using absolute
 url's is not a bug, rather a decision.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/17048#comment:28>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software