WordPress.org

Plugin Directory

Changeset 463391


Ignore:
Timestamp:
11/16/11 05:36:13 (2 years ago)
Author:
MarcusPope
Message:

updated readme with important insights into the usage and support of root relative urls on the web.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • root-relative-urls/trunk/readme.txt

    r462940 r463391  
    4242Traditional relative URLs are bad because any change to your directory structure can change where the content is relative to. 
    4343But Root-Relative URLs are good because you'll always know where they start, and search engines support their usage so you'll have no problems with SEO. 
     44In fact, over 93% of the top 100 websites (according to Alexa) use root relative urls.  Including Wordpres.org, Wordpress.com, Facebook.com, Twitter.com, Google.com, Wikipedia.org, Yahoo.com, Youtube.com, Amazon.com, Fickr.com etc. 
     45Most RSS Feed readers handle them appropriately (notable exceptions include FeedBurner and FeedBlitz) but my plugin takes into account their lack of HTML specification adherence. 
     46 
     47In fact, root relative URL support was established in the very first HTML specification (where it remains today) by Tim Berners-Lee (the real inventor of the World Wide Web) way back in 1993: 
     48 
     49"Where the base address is not specified, the reader will use the 
     50   URL it used to access the document to resolve any relative URLs." 
     51 
     52Some Wordpress core developers think this is "doing it wrong" and "may not be supported in future content platforms like books."  But I can assure you they are a core & valued aspect of the web and are not likely to go away. (I'm currently trying to explain to FeedBurner & FeedBlitz how it's their responsibility to improve their support for the RSS format and not that of others to adhere to an archaic practice like absolute urls.) 
    4453 
    4554= Why doesn't Wordpress use root-relative URLs to begin with? = 
    4655 
    4756Good question.  There are a number of core developers who think the design decision makes an end-user's life easier.  But that's only for those who maintain 
    48 one site and make all of their edits on that site.  Professional web developers would never consider making changes on a production site because if a mistake 
     57one site and make all of their edits on that public site.  Professional web developers would never consider making changes on a production site because if a mistake 
    4958were made (yes even professionals make mistakes) then you have an immediate problem in production.  Instead changes should be made on a development or staging 
    5059server first, thoroughly tested, and then migrated to production as a best practice. 
     
    6170 
    6271Unfortunately no, this plugin is designed to correct new content as it is entered via the administration panel.  It will still work with your current site, 
    63 but it will not alter links you have already embedded.  Because of this inherent defect in Wordpress, this plugin would have no idea if http://example.com/ was a link 
    64 to your staging environment or an external URL, especially if you are accessing the site from http://localhost/. 
    65  
    66 I'm currently working with Brian DiChiara on a solution for find/replace of previous absolute urls into root-relative slashes.  You may still continue to use the link above from interconnectit.com for more information on that process, but we should have the feature included by Nov 20th, 2011. 
     72but it will not alter links you have already embedded.  I'm currently working with Brian DiChiara on a solution for find/replace of previous absolute urls into root-relative slashes.  You may still continue to use the link above from interconnectit.com for more information on that process, but we should have the feature included by Nov 20th, 2011. 
    6773 
    6874= Should I use this plugin if I only have one production site and I make all of my changes in production? = 
     
    94100= 1.2 = 
    95101 
    96 * Discovered an issue with wp-cron.  I've disabled the warnings for now, but I'm not really sure about the potential fallout from the http_host not properly being set in some circumstances. 
     102* Investigated issue with wp-cron... discovered it was an issue with a different plugin altogether, testing showed no problems with root relative urls. 
    97103* Updated plugin to massage rss content urls back to absolute site urls.  This shouldn't need to even happen but unfortunately feedburner and feedblitz don't follow the html spec :(  Google Reader and a bunch of others do however, so there is hope of fixing this problem on feedburner & feedblitz's end. 
    98104* Despite this ticket being not yet patched: http://core.trac.wordpress.org/ticket/19210  I have fixed the previous bugs related to comments_link_feed() or comment_link() functions. 
Note: See TracChangeset for help on using the changeset viewer.