Hello,
I have switched (with your help!) my blog from http to https and the "Enhanced comment area" plugin doesn't work anymore: nothing is diplayed, neither the preview nor the toolbar.
The good news: no error message.
Best regards,
Fabien
Enhanced comment area plugin and https
Enhanced comment area plugin and https
Fabien Chabreuil (blog)
Re: Enhanced comment area plugin and https
That's an old plugin :)
It the plugin configuration, there is a setting for the blog url. Maybe that is still pointing to http://...?
It the plugin configuration, there is a setting for the blog url. Maybe that is still pointing to http://...?
Re: Enhanced comment area plugin and https
Hi onli,
Thank you for your answer.
The plugin configuration was OK and the origin of the problem is not there.
"That's an old plugin "
Oh yes! But what else?
From my point of view, this is one of the biggest shortcomings of S9y. People posting comments don't have a comfortable and modern interface. It's a bit discouraging for some.
Unless there's a solution that I don't know of.
Best regards,
Fabien
Thank you for your answer.
The plugin configuration was OK and the origin of the problem is not there.
"That's an old plugin "
Oh yes! But what else?
From my point of view, this is one of the biggest shortcomings of S9y. People posting comments don't have a comfortable and modern interface. It's a bit discouraging for some.
Unless there's a solution that I don't know of.
Best regards,
Fabien
Fabien Chabreuil (blog)
Re: Enhanced comment area plugin and https
I mean, that's why I built it. But the plain interface also has its advantages.
Did you save the plugin configuration with the new URL? If the URL is correct and the interface does not load there pretty much as to be an error in the browser console when visiting a blog article. Even more so if all you changed recently was the move to https. Maybe send me a PM with the blog url so I can have a look?The plugin configuration was OK and the origin of the problem is not there.
Edit: Or is that the blog in your signature? I assume it is. Look here:
Code: Select all
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://www.chabreuil.com/Aurore/index.php?/plugin/reallivecomment. (Reason: CORS request did not succeed).
Re: Enhanced comment area plugin and https
Alas no. The plugin path is: https://chabreuil.com/Aurore/plugins/se ... vecomment/
Fabien Chabreuil (blog)
Re: Enhanced comment area plugin and https
That's not a path, that's an URI. If it is supposed to be a path then try with the full path instead. (I don't use that plugin so can't tell).
And remembering that you were trying to redirect https://www.... to https://... your page source still contains an awful lot of https://www.... href and src, so your configuration contains the www in at least one place.
And remembering that you were trying to redirect https://www.... to https://... your page source still contains an awful lot of https://www.... href and src, so your configuration contains the www in at least one place.
Running s9y at https://erack.net/blog/
Re: Enhanced comment area plugin and https
But https://www.chabreuil… is converted to https://chabreuil...
And in the plugin, the parameter is named path but the example is an url…
And in the plugin, the parameter is named path but the example is an url…
Fabien Chabreuil (blog)
Re: Enhanced comment area plugin and https
Oh, did I mix that up? No, here path is meant to be an URL :) That's a bit confusing, but the example is correct.
The thing is: In your blog it is pointing to https://www. That means that either there is no path set and it is falling back to the configured baseUrl, and that one is wrong. Or there is the wrong path set in the plugin. I don't see a third option. And it completely explains why the plugin does not work.
The thing is: In your blog it is pointing to https://www. That means that either there is no path set and it is falling back to the configured baseUrl, and that one is wrong. Or there is the wrong path set in the plugin. I don't see a third option. And it completely explains why the plugin does not work.
What your server does with the call does not matter. As long as the url is pointing to a subdomain, CORS will block the Javascript file. It can not know that the two are identical and controlled by the same person. It has to point to https://chabreuil... on the non-www domain and to https://www.chabreuil… on the www-domain.But https://www.chabreuil… is converted to https://chabreuil...
Re: Enhanced comment area plugin and https
Hi Fabian,
Nice blog. I wonder how you setup your 'archive' area. Is that a plugin? Do dated posts automatically get transferred to the archive area or is that a manual task for you?
Cheers,
Dave
Nice blog. I wonder how you setup your 'archive' area. Is that a plugin? Do dated posts automatically get transferred to the archive area or is that a manual task for you?
Cheers,
Dave
Re: Enhanced comment area plugin and https
Ah... forget my last question... .I see how you did it now.
Regards
Dave.
Regards
Dave.
Re: Enhanced comment area plugin and https
@onli:
Yes, the address of the blog in the configuration was https://www. I suppress the www and it works now. Thanks a lot.
@DaveVK
I use 2k11 template. The archive area is a only a link in the navbar of the template : /Aurore/archive
Best regards, Fabien
Yes, the address of the blog in the configuration was https://www. I suppress the www and it works now. Thanks a lot.
@DaveVK
I use 2k11 template. The archive area is a only a link in the navbar of the template : /Aurore/archive
Best regards, Fabien
Fabien Chabreuil (blog)