When you click on a link, or when you see an image in a page, each of these events causes your web browser to send a request to the web server that lives at the address in the link. For example, if you click on a link to Google's "About Google" page, your browser sends a request to the webserver at the address www.google.net and requests a page with the filename about.html; if there's a picture, your browser sends a request to the webserver that hosts that image. If it's an image, it usually it's at the same address as the page you're looking at, but not always; when you look at the church sign photo gallery, for example, the website address is the same, because the images live on the same website as the page that displays them.
When your browser sends out these requests, it sends several bits of information as part of that request, such as the name of the browser program you use (such as Internet Explorer or Firefox), the language your browser uses (English, if you're reading this) and so on. One of these bits is the website address of the page you just clicked or that shows the image. This is is called the referer, because the link or image on this page refers to the target address. The Church Sign Generator picks up on that referer information and looks at it to determine if someone has put a direct link to an image. The way it does that is to see if the referer address is from the churchsigngenerator.net domain, and if it isn't, it won't allow the image to be sent out.
What this means is that if you look at the churchsigngenerator.net website and it loads an image on the site, it will be shown, but if you look at some other website and it tries to load an image that is on the churchsigngenerator.net site, it won't allow it. The reason for this is that there are so many websites out there that try to do this "remote linking" of images on this site, and if I allowed it, it would cause a tremendous number of images to be sent out. I have to pay the.netpany that provides my web hosting service for all the data that gets sent out each month, so allowing all those other websites to link directly to images on my site would cost me tons of money.
There are several ways that the information your browser sends out can be blocked so that it isn't sent to the server. The most.netmon way is for a program to be installed that intercepts the request and purposely strips out or alters that information, usually to protect your privacy. This kind of program is usually called a firewall or a proxy. It can be a program installed on your.netputer (such as Norton Personal Firewall or similar firewall programs), or it can be something your network administrator or internet service provider has installed on their network. If there is a firewall or a proxy that blocks the referer information your browser sends out, then you may not be able to see images from churchsigngenerator.net at all. If this is the case, you may have to call your network administrator or internet service provider and ask them how to fix it.