Sorry, I mean not index page I meant photo page, check the source code it has 8 http links. 

yes was widget in side bar i have removed it

you can see the padlock not locked and i enable photo widget on index 

it will show unlocked now

Just check the source code, as I said it has a lot of http links, which is why the padlock is not locked. 

yes and as i said it was add this widget in side bar and i have removed it so you can see photos page breaks the ssl

look index now with photo widget enabled ssl broken 

Tammy, please open the source code of the index page and see how many http links you have on index page. Make them https first. 

look dashboard  ssl broke from usecarosel it uses images from photos and it breaks ssl to if i disable it ssl fine

same with photo caresel it use photos it breaks ssl

profile photo widget breaks ssl on profiles 

ross when you looked the page yes it had link from add this in a side var widget and images in movie roll that are http

index  with out photo widget

green padlock locked

index with photo widget

padlock broken

and i dont know how but the images in newsfeed from photo plugin break the seal to 

just comment on a photo it goes to newsfeed and breaks ssl 

a image upload into newsfeed are fime

why no padlock test photo page
https://www.whynopadlock.com/

every thing is called secure

but the padlock is broken

and the same for every page that has images from photo plugin

everything secure but padlock broken

???

2 months now since i bought this problem up

can some one please look at why photos page and photos widget and every onthe page that has images from photos plugin breaks ssl

Tammy, let's do the following, please make all http: links https: and disable photo widget on index page. As soon as you do that let us know. 

ok photo widget disabled and page locked

Tammy, please PM me your admin details. 

Tammy, turns out this is the code:  <img src="javascript:void(0)" class="ow_photo_img ow_photo_view" /> which breaks ssl padlock, it belongs to the photo plugin. Turns out Google Chrome considers this: "javascript:void(0)" as insecure, however Firefox does not. 

We have reported this to the developers, it will be fixed in one of the upcoming updates. 

cool thanks for taking the time to look at the problem 

hi can somebody help? which is the source code that i have to edit the http to https?

also is there a quick guide to switch to https?

many thanks