[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:  closed   
 Priority:  normal           |    Milestone:           
Component:  General          |      Version:           
 Severity:  normal           |   Resolution:  invalid  
 Keywords:                   |  
-----------------------------+----------------------------------------------
Changes (by Otto42):

  * status:  reopened => closed
  * resolution:  => invalid


Comment:

 Replying to [comment:5 hakre]:
 > 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.

 I'm sorry, but you are mistaken.

 If I have a permalink that looks like this:

 http://example.com/blog/2009/name-of-post

 And it contains a relative image link, like "image.jpg", then that is
 going to resolve to http://example.com/blog/2009/name-of-post/image.jpg by
 the browser.

 The problem is that image.jpg does not exist there, as the entire
 permalink structure (everything after "blog") is pretend. It's make-
 believe. The directories don't actually exist. That's what the rewriting
 is all about.

 > 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:

 Umm.. No. Sorry, but you're wrong again. Here's two examples:

 IMG SRC="/blog/uploads/2009/image.jpg"
 IMG SRC="image.jpg"

 Both of those are relative. The first one is root-relative (as it include
 the leading /) , and using that format would actually work. A browser
 would not resolve it from the current path, but from the current domain
 (the leading slash makes it do that).

 > 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."

 In order to disprove that nonsensical claim, it would first have to be
 demonstrated at all in some way. The idea that one-way or another-way is
 for "noobs" is simply ridiculous on the face of it.

 Relative URLs make sense in some situations, and absolute URLs make sense
 in others. There is never a one-size-fits-all solution, and only "noobs"
 would think otherwise. ;-)

 > 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.

 I am aware of that. It's a problem, admittedly, but if you've examined the
 importer, there's a method it uses to correct those links when you use an
 Export/Import and migrate attachments in that manner.

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

 Closing it as invalid again, because it is. Don't reopen it without some
 form of, you know, logic. Or at least knowing what you're talking about.

 Also, Trac is not the place for debate on whether something is a good idea
 or not. Take it to wp-hackers if you want to debate it.

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