[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:  closed
 Priority:  normal           |   Milestone:
Component:  General          |     Version:  3.3
 Severity:  normal           |  Resolution:  maybelater
 Keywords:  close            |
-----------------------------+-------------------------

Comment (by edwardw):

 Replying to [comment:52 MarcusPope]:
 > Oh, and the plugin is now available for download, so enjoy!
 >
 > http://wordpress.org/extend/plugins/root-relative-urls/

 Just tried the plugin, and it pretty much accomplishes pretty much what my
 test patch and the core devs' hacky fixes (WP_HOME/WP_SITEURL). My main
 concern right now is that previous content (internal posts, media,
 images/video) is not automatically updated - for example, if previously
 server was based off internal1.example.com it would break to outsiders
 looking at blog.example.com (Although I'm sure we can always find&replace
 in the database for old posts)

 Also a nice enhancement, but not necessary (would help with web mirroring,
 but that's going off a bit on a tangent) would be to use relative URLs
 directly in page source - instead of

 {{{<link rel="wlwmanifest" type="application/wlwmanifest+xml"
 href="http://internal1.example.com/wordpress/wp-includes/wlwmanifest.xml"
 /> }}}

 we can go directly to this:

 {{{<link rel="wlwmanifest" type="application/wlwmanifest+xml"
 href="/wordpress/wp-includes/wlwmanifest.xml" /> }}}

 Finally, which domain gets to be the "preferred" one for sending out
 e-mails? Right now on my development server it seems to the the one I
 installed from.

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