Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

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 risposte
  • 49 hanno questo problema
  • 2 visualizzazioni
  • Ultima risposta di 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.

Tutte le risposte (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.