Force HTTPS of google-analytics.swig. Again.#881
Force HTTPS of google-analytics.swig. Again.#881ivan-nginx merged 1 commit intotheme-next:masterfrom hsiangfeng:patch-1
google-analytics.swig. Again.#881Conversation
No "https" will result in an error。
|
What's the error? |
|
I think there is no error because auto-protocol must be used. But need to test it: can GA use link without schema or not? @stevenjoezhang u approve it, but u test it? Test old method? Test new? |
|
The organic rate will not be able to obtain GA. It is recommended to use "https" directly because it sometimes becomes "http" I have encountered。 |
|
What's this «it sometimes becomes "http"»? If site proto http, http will be used; if https, will be used https. All another similar 3rd-party services working like that. I think if protocol of website will be http, GA with your changes (https) will not work. Can u provide more info about that GA usage recommendations? Alright, I see now. |
There was a problem hiding this comment.
It seems that fix-unfix was changed many times: #580
But in accordance with that comment and check both links directly I think more reasonable will be usage with force https proto.
google-analytics.swig. Again.
|
Seems fonts need to be fixed too: |
No "https" will result in an error
* tag 'v7.1.2': Release v7.1.2 Quotes in Release Drafter for around possible bugs Add Icons in Release Drafter Expressions and translations in CONTRIBUTING.md (theme-next#885) Fix Release Drafter template `External Change` label added Change the internal path of quicklink (theme-next#883) Improve Docs section in PR template Force HTTPS of `google-analytics.swig`. Again. (theme-next#881) Update Facebook Graph API to v3.3 (theme-next#876) Fix a few typo errors in docs (theme-next#864) Changed Telegram group link to Chinese Fix Github gist bug (theme-next#861) Update symbols_count_time (theme-next#862) Release v7.1.1
No "https" will result in an error
No "https" will result in an error。
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue resolved: N/A
What is the new behavior?
How to use?
In NexT
_config.yml:Does this PR introduce a breaking change?