This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

On www.ownerbuilderbook.com website, I was always able to see posted photos in the past. Now, the photos appear to be blocked, showing a "torn page" icon. What do I do to be able to see posted photos?

  • 2 amsoshi
  • 49 sa na da wannan matsala
  • 1 view
  • Amsa ta ƙarshe daga consultutah

more options

I've not changed any settings. Could this problem be the result of routine upgrades from Firefox, as in some type of blocker? Other photo sites (Facebook, email, etc) allow photos to come through. This photo blocking only seems to occur on this website.

I've not changed any settings. Could this problem be the result of routine upgrades from Firefox, as in some type of blocker? Other photo sites (Facebook, email, etc) allow photos to come through. This photo blocking only seems to occur on this website.

All Replies (2)

more options

It is possible that you clicked "Block Images" in the right-click context menu while saving an image.

See:

You can use these steps to check if images are blocked:

  • Click the "More Information" button to open the "Page Info" window with the Security tab selected (also accessible via "Tools > Page Info").
  • Go to the Media tab of the "Tools > Page Info" window.
  • Select the first image link and scroll down through the list with the Down arrow key.
  • If an image in the list is grayed and there is a check-mark in the box "Block Images from..." then remove that mark to unblock the images from that domain.
more options

This was a problem with the site's DNS provider. It has been resolved.