SSL – Securing Pages

Viewing 10 replies - 1 through 10 (of 10 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    9 years, 3 months ago

    1. Clear your cache and then disable the caching plugin.

    2. Using the plugin “better search and replace”, search for http://www.reliefteaching.com and replace with https://www.reliefteaching.com (no trailing slashes).

    3. When done (not in dry run mode), re-enable your caching plugin.

    Thread Starter rwbra

    (@rwbra)

    9 years, 3 months ago

    Done, Done and Done.

    Thank you so much.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    9 years, 3 months ago

    Once done, you can delete the plugin “better search and replace”.

    Thread Starter rwbra

    (@rwbra)

    9 years, 3 months ago

    Thanks for your help Steve.

    I have some pages eg https://www.reliefteaching.com/relief-teacher-pay-rates/relief-teaching-pay-and-conditions/ which by all tests on whynopadlock.com and other similar sites is secure with all links also secure but does not generate a padlock.

    More importantly My membership payment page https://www.reliefteaching.com/membership/executive-annual/ is the same. It is tested as secure but does not general a lock giving an “attackers might see images ….” message.

    Even after clearing cache etc the SSL lock is not featured. Any ideas?

    Thread Starter rwbra

    (@rwbra)

    9 years, 3 months ago

    Even when I start a new page with NO CONTENT the SSL secure padlock does not show up.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    9 years, 3 months ago

    Your pages request this link: http://www.reliefteaching.com/wp-content/uploads/2016/11/looking-for-something.png

    When you ran the plugin did you make sure that you UNCHECKED “dry run” and selected all tables *and* you cleared all caches?

    By the way, I just ran “whynopadlock” against my site and got incorrect results. I wouldn’t trust it for anything definitive.

    Thread Starter rwbra

    (@rwbra)

    9 years, 3 months ago

    I thought I did, Steve. I ran it again and double checked UNCHECKED Dry Run. It processed the whole 118 tables.

    I cleared cache. Rebooted but the same result.

    Thank you for your help.

    Bob

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    9 years, 3 months ago

    Maybe it’s in source someplace and not in the DB.

    Try using this to search: https://wordpress.org/plugins/string-locator/

    j09

    (@j09)

    9 years, 3 months ago

    Just to add to the insights shared by @sterndata

    @rwbra Some of your pages have mixed content – http:// or (non-secure) requests on a https:// or (secure) connection – and that’s why they don’t have the lock.

    Really Simple SSL is by far the simplest fix that I know of for this particular issue. it forces everything to go through https://

    • This reply was modified 9 years, 3 months ago by j09.
    • This reply was modified 9 years, 3 months ago by j09.
    Thread Starter rwbra

    (@rwbra)

    9 years, 3 months ago

    I think it must be in one of the widgets. It only happens on pages with side bars. I can track it down from here. Thanks for your help Steve.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘SSL – Securing Pages’ is closed to new replies.

Tags