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

WordPress Trac wp-trac at lists.automattic.com
Thu Oct 27 23:52:00 UTC 2011

#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 MarcusPope):

 @ryan - It may not seem worth the pain to you, but it has and will
 continue to prevent wordpress from being a serious contender in a majority
 of enterprise situations for reasons that are exclusive to an unmanageable
 build & deployment process.

 Several points, like internal v external NAT translations, reverse-
 proxies, ip access on load-balanced configurations or even just hosting
 multiple tld sites on one installation have in fact been ignored.

 And honestly the amount of code surrounding all of the URL & PATH
 constants, and HTTP/S hacks, and the very existence of those values
 permeating the DB are pretty much proof positive that more pain was added
 to the equation than would have been necessary to refactor it back in 2007
 when this concept was first proposed (possibly even earlier than that.)

 I applaud your honesty in recognizing the value in a root-relative design,
 you're the first to do so without making up excuses that it can't possibly
 be done - ala dd32.  And feel free to assume we are an easily amused
 group.  But expecting a hero to come change the entire underlying
 architecture for your interested review doesn't start with the feedback
 we've seen here.

 Ideally we'd see a forked version that the entire group stands behind
 because it's the proper way to do it.  Users would have a choice of when
 to migrate. And eventually the lesser of the designs would be sunsetted.
 Root-relative urls are 99% identical to absolute URLs so the mass
 casualties are not likely.  And if a plugin doesn't work as a result it's
 most likely because it operates on the same flawed assumptions and needs
 to change as well.

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

More information about the wp-trac mailing list