Skip to content
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.

Protocol Relative URL not compatible with CDN Rewrites #546

Closed
justinpage opened this issue Nov 8, 2015 · 3 comments
Closed

Protocol Relative URL not compatible with CDN Rewrites #546

justinpage opened this issue Nov 8, 2015 · 3 comments
Labels

Comments

@justinpage
Copy link
Contributor

Per PR #430

Problem

Protocol Relative Theme Assets Plugin takes advantage of adding filters to common src methods. This includes: style and script loader src. This takes precedence over any CDN Rewrite tool that may require a different URL.

Discussion

We currently use CDN Linker. When this plugin is activated and setup, it rewrites our assets from within wp-content folder to point to our CDN. It appears when we use both this and FoundationPress, the protocol relative plugin takes place last and therefore over any CDN Rewrite.

It would be best to allow the user to decide whether or not they want to use a protocol relative url plugin. Since this plugin is built-in to the theme, it forces all to use it. One possible solution would be to remove it and list it in recommended plugins in the readme. The theme should not make the assumption that all would want to use the plugin.

@olefredrik
Copy link
Owner

@KLVTZ : I see the challenge. You have a valid point. Let's remove it from the framework and let people decide whether the plugin should be installed or not. I'll add it to my todo list.

@olefredrik olefredrik added the bug label Nov 18, 2015
@justinpage
Copy link
Contributor Author

👍

@olefredrik
Copy link
Owner

Fixed #562

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants