Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Parts of this page are not secure such as images

  • 6 trả lời
  • 1 gặp vấn đề này
  • 2 lượt xem
  • Trả lời mới nhất được viết bởi in4m8n

more options

Hi folks. The title of this question started 2 weeks ago. Was fine before, but now a yellow triangle on the padlock.

Running test sites show everything secure. I have certificates. No other browser shows a warning. I read your help article and all is just like it should be. .htaccess redirects domain.com to www.domain.com and http: to https: just as it should. But still this "error". It must be images in my header, footer and sidebar, but I cannot change the path for those in any way I can find.

How can I correct this?

Thanks!

Hi folks. The title of this question started 2 weeks ago. Was fine before, but now a yellow triangle on the padlock. Running test sites show everything secure. I have certificates. No other browser shows a warning. I read your help article and all is just like it should be. .htaccess redirects domain.com to www.domain.com and http: to https: just as it should. But still this "error". It must be images in my header, footer and sidebar, but I cannot change the path for those in any way I can find. How can I correct this? Thanks!

Tất cả các câu trả lời (6)

more options

You can check the Web Console for messages coming over an open HTTP connection and also check the Network Monitor for links with a crossed padlock.

Được chỉnh sửa bởi cor-el vào

more options

Thanks. I can view source and see which images are http. Just no way on Wordpress to correct them. Must be something than can do it. The Search and Replace addin did not help. I tested on a staging site. But I cannot get to raw code to change this at the site.

That said, I will look at your links. But finding the offender is nmot the isue. Fixing it is.

And is this a recent change to FF? I never saw this before 11/18/22

more options

I have fixed all except for one page where I cannot find the error. Once I learned how to see the http: in the code, was not so hard.

more options

Using view source on that page, no http: shows up. Cannot find the issue. All other pages fixed. If any ideas why this is the only page that did not show something obvious, I'd appreciate it. Thanks.

more options

Can you post a link to a publicly accessible page (i.e. no authentication or signing on required)?

more options

I'd prefer no to publicly. But now have found out it is the NGG Gallery. Seems to be a known issue. Working on it.

Learning experience today :)