[wp-trac] Re: [WordPress Trac] #6599: Inpage URLs can be realtive instead of being always absolute.

[WordPress Trac]

#6599: Inpage URLs can be realtive instead of being always absolute.
-----------------------------+----------------------------------------------
 Reporter:  hakre            |        Owner:  anonymous
     Type:  feature request  |       Status:  reopened 
 Priority:  normal           |    Milestone:           
Component:  General          |      Version:           
 Severity:  normal           |   Resolution:           
 Keywords:                   |  
-----------------------------+----------------------------------------------
Changes (by hakre):

 * cc: hanskrentel@… (added)
  * status:  closed => reopened
  * resolution:  invalid =>
  * type:  enhancement => feature request


Comment:

 I've missed the comments here for quite some time. But that is no problem,
 since the topic itself did not change since all the versions:

 Replying to [comment:1 Otto42]:
 > This is incorrect. Replacing these absolute URLs with relative ones will
 break all non-default permalink systems.

 '''Permalinks Argument:'''
 "A permalink, or permanent link, is a URL that points to a specific blog
 or forum entry after it has passed from the front page to the archives"
 ([http://en.wikipedia.org/wiki/Permalink Definition by Wikipedia])

 Because a Permalink is an URL/URI, writing it as a relative or absolute
 one does not make any difference. Your argumentation just fails here.

 Replying to [comment:1 Otto42]:
 > Recognize that relative URLs work in one of two ways:
 >  * from root
 >  * from the current URL
 Another misunderstanding. Relative URLs are always built upon the current
 URL -or- the BASE element. The term "from root" is misleading here and
 only named so that you can start another invalid and misleading
 argumentation:

 Replying to [comment:1 Otto42]:
 > Using root level relative URLs would break WordPress's ability to be
 easily installed in a subdirectory of a site.
 That it was. I will just ignore this further to better pinpoint the rest.

 > Using current URL relative links breaks permalinks, because the point of
 permalinks is that they bear no relationship to the underlying file system
 structure of the site. What is a single relative link to, say, a CSS file
 that works when the current URL is both http://example.com/blog/ and
 http://example.com/blog/2008/04/15/single-post/ ?


 > No, we use absolute URLs for a very good reason, and those absolute URLs
 are built on the fly from the settings.

 Well if there would be "a very good reason", then please name it. Or proof
 the Opposite of: "Using absolute URLs (and/or the BASE Element) in Webapps
 is for coding noobs. This is done by those who did not understand how
 links work or who do not want to solve linking properly and stable."

 > The site remains portable when coded correctly (using bloginfo('url')
 calls and similar to display the root URL instead of hardcoding it.
 Have you ever taken a look how WordPress does link to files? That is all
 but _not_ done properly. In opposite to what you write, the URLs hard
 hardcoded into the content and not generated by "using bloginfo('url')"
 when the page is displayed.

 > Closing this as invalid.
 Re-Opening this as feature request. It's not invalid and many pplz. over
 and over dicuss about this in the community.

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