Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #32639, comment 4


Ignore:
Timestamp:
12/22/2015 02:38:14 PM (9 years ago)
Author:
mattfiocca
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #32639, comment 4

    initial v1  
    11@SergeyBiryukov , thanks for sharing that design decision link. I think each of the points made there could be addressed in my feature request though:
    22
    3 '''RSS Readers''': the application would still display absolute urls, they just wouldn't be stored in the DB absolutely. Its my understanding that RSS readers aren't pulling content directly from the database, but are rendering an xml template. In this RSS template, you would use permalink and site_url() functions for a resource, and these functions could return the domain, blog root (/blog, if set that way for example), and the relative URI from the database concatenated together to form the absolute URL.
     3'''RSS Readers''': the application would still display absolute urls, they just wouldn't be stored in the DB absolutely. Its my understanding that RSS endpoints aren't pulling content directly from the database, but are rendering an xml template. In this RSS template, you would use permalink and site_url() functions for a resource, and these functions could return the domain, blog root (/blog, if set that way for example), and the relative URI from the database concatenated together to form the absolute URL.
    44
    55'''Permalinks''': The root-relative issue would be addressed with the introduction of the BLOG_ROOT config constant (or even an entry in the wp_options table).