Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #15928, comment 82


Ignore:
Timestamp:
11/08/2014 01:10:04 AM (9 years ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15928, comment 82

    initial v1  
    66Ideally we should use protocol relative URLs when inserting local content in the editor. However there are so many places that check for `https?://` when looking for URLs that using only `//` would need extensive back-compat fixes. And even then some plugins would probably break.
    77
    8 The alternative is to replace `https://local.domain` with `//local.domain` on the front end when the site is accessed through http. That would be yet another display filter and should run after everything else. This still could break plugins that use JS to look for images, etc. but will be more backwards compatible.
     8The alternative is to replace `https://site.domain` with `http//site.domain` (or perhaps better with `//site.domain`?) on the front end when the site is accessed through http. That would be yet another display filter and should run after everything else. This still could break plugins that use JS to look for images, etc. but will be more backwards compatible.