I'm having problems on a website after adding an SSL certificate. These are the WhyNoPadlock results:
What I’ve done so far:
- Changed all to HTTPS in WP settings
- Used Better Search Replace to replace all instances of HTTP with HTTPS.
This hasn't fixed things and any advice on how else to resolve these hard and soft failures very appreciated.
Another problem is that since adding the SSL certificate, the slider which should appear on the home page has disappeared. It uses an old plugin called Cross Slide Cross Fade, which hasn’t been updated for a few years. I’m presuming this may also be a result of a mixed content error but any other thoughts on this also appreciated. I'm hoping it's simply a question of sorting out any http/https conflicts in it but also wonder if push comes to shove if it would be better to uninstall it and try using a more modern slider plugin?
Many thanks
I'm having problems on a website after adding an SSL certificate. These are the WhyNoPadlock results: https://www.whynopadlock/results/7193cea2-78e7-4bc7-9581-2af7f90bd15d
What I’ve done so far:
- Changed all to HTTPS in WP settings
- Used Better Search Replace to replace all instances of HTTP with HTTPS.
This hasn't fixed things and any advice on how else to resolve these hard and soft failures very appreciated.
Another problem is that since adding the SSL certificate, the slider which should appear on the home page has disappeared. It uses an old plugin called Cross Slide Cross Fade, which hasn’t been updated for a few years. I’m presuming this may also be a result of a mixed content error but any other thoughts on this also appreciated. I'm hoping it's simply a question of sorting out any http/https conflicts in it but also wonder if push comes to shove if it would be better to uninstall it and try using a more modern slider plugin?
Many thanks
Share Improve this question asked Jun 17, 2020 at 11:04 user152362user152362 11 bronze badge 6 | Show 1 more comment1 Answer
Reset to default 0You have version 1.6.0 of the crossslide plugin. (I'd guessed 1.5.2 since the changelog said 1.6.0 fixed this, but it didn't.)
You can fix this by
unticking the 'Default jQuery' option in the plugin configuration, which removes the ajax.googleapis/ajax/libs/jquery/1.3.2/jquery.js include
replacing
$(
withjQuery(
on lines 101 and 102, i.e. instead of$(function(){ $('#crslideshow').crossSlide({
you should have
jQuery(function(){ jQuery('#crslideshow').crossSlide({
(This is because WordPress sets up jQuery in noConflict mode by default, where it does not define itself as $. Including the second jQuery script did set up $ with the old version.)
Here's a gist of roughly what you should be left with. (There is another set of $(
to jQuery(
changes on lines 120-133, but you don't need those for the mode you're running the plugin in.) It should now work again. The original CrossSlide author does recommend using something more modern, but it should continue to work fine.
You could also upgrade the plugin to 2.0+ which would already contain this fix; it's not available for download anymore, but the files are in subversion (see the 'Development' tab of the plugin page).
$()
notjQuery()
. The plugin changelog says it should be fixed in version 1.6 - can you get hold of a later version? There's a version 2.0.5 in Subversion if you can get it from there. Alternatively you can probably just edit the http:// to https:// in the plugin, or change the two$(
tojQuery(
and it should work again. – Rup Commented Jun 17, 2020 at 11:33