[wp-trac] [WordPress Trac] #38148: Do not store URL protocol in the database

[WordPress Trac]

#38148: Do not store URL protocol in the database
-------------------------+------------------------------
 Reporter:  aristath     |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Formatting   |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  https        |     Focuses:
-------------------------+------------------------------

Comment (by mdgl):

 Thinking more radically, why do we store explicit URLs that reference
 other WordPress managed content in any case? Shouldn't these be expanded
 dynamically as we generate the page, for example if we stored something
 like a shortcode in the database `[objref id="2392"]`? This would allow us
 to deal with the http(s) issue, enable users to change slugs/permalinks as
 they wish and create great filtering opportunities for developers.  Of
 course you would still need to be able to insert absolute URLs if you want
 for references to external sites and other special cases.  In my view, a
 clear distinction between such "internal" and "external" links would be
 quite helpful.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38148#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform