Logging in | File names | Keeping track | Banner ads | FTP clients
Don’t just bookmark www.angelfire.com
. Instead, after you log in to your account, bookmark the Angelfire Web Shell.
The Web Shell lets you upload pages, create directories, and edit your pages on the server. Once you have logged in, Angelfire sets a “cookie” in your browser and automatically logs you back in each time you visit the Web Shell with that browser.
If you share your computer or do not want an automatic login, then clear the “Sign me in automatically” checkbox on the Login page.
If you login at a computer other than your own, you may also want to clear the browser cache when you are finished. (See the browserÕs settings or preferences.)
Angelfire has a few special rules about file names. (They do not apply to every web server.)
Rule No. 1: Always be sure you are editing the most up-to-date version of a file. Beginners often change a document on the server but forget to update their local copy. Then they upload the local copy to the server — and their changes are gone.
Best method: Keep copies of your HTML files on your own computer (the “local machine” or “local host”). You should have a local folder that exactly reproduces the contents of your Angelfire directory (the “remote” location). Make changes to your local files first, then upload them to Angelfire, either with the Web Shell or with an FTP client.
When uploading files to Angelfire from a Windows PC, be aware that file names of eight letters or fewer may be automatically capitalized by Windows, or possibly set in uppercase. But this is not the case on every Windows PC.
You can use the Web Shell to edit files on the server, but donÕt forget to update your local copies as well. The easiest way — and it’s not very convenient — is:
Of course, you can visit your site with your browser and view page source. But if you want to make changes, you must delete all of the banner ad code first. It’s easiest to work with the files on your local machine.
Banner ads will appear at the top of every Angelfire page be default. (This is how Angelfire attempts to pay for its free hosting service.)
You have the option of having ads appear in pop-up windows rather than at the top of each page. You can change your preference at the Angelfire Web Shell; here you can also make small changes to the ads’ appearance.
You can avoid the ad banners entirely by omitting the <BODY>
tag from your code! HTML 4.01 documents are valid without a <BODY>
tag, but in some cases you will still want to leave <BODY>
in place. The CSS body
selector will work even if the HTML <BODY>
tag is not present.
If you use a browser to view the source for one of your pages, you will see a long block of ad-related code. Delete everything from the comment <!-- Start of Angelfire Ad Code -->
to the comment <!-- End of Angelfire Ad Code -->
.
When viewed with Netscape 4.7 or earlier, Angelfire banner ads may cause serious errors on the page. (Sorry, there’s nothing we can do about that; it’s a flaw in the Angelfire ad code.)
If you want to use an FTP client to move pages to and from your Angelfire site, all you need to know is your server name, username, and password.
ftp.angelfire.com
https://www.angelfire.com/al4/rob0
then your username is al4/rob0
undefined