We have changed our pages from http to https. Now webyep doesnt show the editor anymore. What can it be? When I open th lock, a window shows up with an html Code inside.
Did you change the source for the JavaScript from HTTP to HTTPS also? If the outer page and the inner elements don’t have the same security origin, browsers will often keep JS from working as a security measure. You may need to edit the WebYep Action to do this – I am not certain how it sources those files.
Also, can you post a link to the page that should be able to be edited? I don’t think I would need the password to see the error, right?
Walter
On Nov 15, 2016, at 6:35 AM, Thomas email@hidden wrote:
We have changed our pages from http to https. Now webyep doesnt show the editor anymore. What can it be? When I open th lock, a window shows up with an html Code inside.
If the file references do not include http in that file, then there’s nothing to change. If the files are referenced from Google’s “ajax” CDN, with full URLs instead of file paths, then the prefix will need to be changed from http:// to https://. If the files just have partial (relative) paths, like ‘…/Resources/somefile.js’, then they will already be served under HTTPS, using your certificate, from your server. That is the very best way that this sort of thing would be handled, and what I imagine is actually the case.
Walter
On Nov 15, 2016, at 8:43 AM, Thomas Kimmich email@hidden wrote:
it’s for sure (and as far as I remember) the editor_init file such as
tinymce_init.php
In there, there are several resources to be pointed to. Check them - and change if required.