Hard-coded protocol resulting in secure-nonsecure warning
Opened this issue · 2 comments
thdoan commented
If this plugin is used on a secure page, then it will throw a secure--nonsecure mixed content warning.
FIX: Remove the hard-coded protocol ("http:") from line 190.
justinkwanlee commented
I just pushed a fix for this, hopefully it gets merged in
#11
Tastaturberuf commented
👍