noosfero | Hard-coded http causes mixed-content warnings on https environments (#57)

[Ewout ter Haar]

New comment for Issue 57

https://gitlab.com/noosfero/noosfero/issues/57#note_1141354


Author: Ewout ter Haar

@terceiro Most links are working. It's just that in some places there are still references to http, for whatever reason. I'll give some examples (where using 1.1~rc3 now, or at least a package derived from that).
1. https://social.stoa.usp.br/ewout/gallery/screenshot-from-2014-09-04-22-38-18.png?view=true : Blocked loading mixed active content "http://www.google.com/recaptcha/api/js/recaptcha_ajax.js" (what is recaptcha doing on that page? Some plugin?)
2. (Need to be logged in) Everywhere where TinyMCE is loaded : Blocked loading mixed active content "http://social.stoa.usp.br/stylesheets/tinymce.css" + Blocked loading mixed active content "http://social.stoa.usp.br/"
3. (maybe unrelated) Editing a post, inserting midia, trying to amplify an image before inserting into tinymce: a popup references a broken image, https://social.stoa.usp.br/myprofile/ewout/cms/undefined

Not really mixed-content, but still annoying: links to http:// in href atributes: all links to profiles. See https://social.stoa.usp.br/. The src atributes are ok, but the href links to http:// URLs.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listas.softwarelivre.org/pipermail/noosfero-dev/attachments/20150424/360334f5/attachment.html>