AutoPost Pro Overview

  So, How Does This Thing Work?

In this file, we will give you a quick overview of the basic functionality of the software.

AutoPost Pro is a picpost script - hopefully you know what a picpost is by now since you have already purchased the software. The software allows outside webmasters to come to your site and post their pics on your site. This gives you fresh, bookmarkable, content to keep your surfers pleased.

Posting Pics

For a webmaster to post a pic, you need to direct them to the post.cgi script. Any old link to that script will do. Once they get there, they will fill out a form with all the information that is needed to make a post. When they hit submit, their URLs are verified (optional), reciprocal links are checked (optional), and their posting is then added to the queue database. Then, it's all up to you and/or your moderators to complete the task.

From the administrative script, you will be able to approve, edit, and/or reject posts in the queue database. It's up to you to determine what posts make the cut, and which ones don't. After you have approved posts, you will need to rebuild the main and archives pages so they display the current posts in the databases. This is done through the administrative script, and you will need to do it each time you approve, edit, or delete posts.

Maximum Posts Per Submitter

In setup.cgi you will set the maximum number of posts allowed per submitter. When someone submits a pic, the script will check the e-mail address, domain name, and IP address to see how many similar posts have been made. It adds up the total amount of similar posts found in both the queue and current database. If any of those three (e-mail, domain, IP) exceed the maximum amount allowed, the post will not be accepted.

For example, lets say you have the max number set to 3 and you have several posts in your queue and current databases. Now, John from the IP comes to make a post; his e-mail address is and the URL he is submitting is The script will go through the queue and current databases searching for posts made from, with the e-mail address, or from the domain Let's say the software comes up with the following results:
In the current database:
2 posts from
1 posts from
0 posts from

In the queue database:
0 posts from
1 posts from
1 posts from

Total in queue and database:
2 posts from
2 posts from
1 posts from
In this case, the post would be accepted. None of the total values above met or exceeded the limit of 3 posts. If any of the above total values had been 3, the post would not have been accepted. Notice that the archives are not checked - this allows the user to make more posts once some of his older postings have been moved to the archives or deleted.

Automated Posting and Partners

If you have come to trust certain people that have been posting to your picpost, you can make them a partner. This will allow them to make instant additions to your picpost - no moderation will be required. Once you have added a partner, point them to the partner.cgi script so they can make postings. They will fill out the necessary information on that page, and their post will be instantly added to the current database. The main page will also be updated at the same time, so there is no need to rebuild them after a partner has made a post.

If your partners need to be reminded of their password, or want to update their partner details, point them to partner.cgi?remind and partner.cgi?login, respectively.

Posts made by partners can also be made to stand out against the normal posts. Through setup.cgi you can tell the script to use different colors and font sizes for partner posts. Additionally you can add "icons" to partner accounts, and those icons will then be displayed next to each of your partners posts. These icons can contain any HTML you want, so they can be used for a wide range of purposes. Icons can be added to partner accounts when they are created, or by editing a partner account.

How They Are Listed

So, now you've got some posts in your database, but how are they listed? Well, once a post has been approved it goes into the current database. This database stores all of the posts that are currently visible (but not in the archives), and holds posts from all categories. When the posts are written to your main page, the newest postings are printed at the top and the oldest at the bottom. Now, in setup.cgi you entered a maximum number of posts to list. Once the current database exceeds that number, the oldest posts are taken out and placed in the archives. The archives are split into categories, so there is a seperate page for each one. Posts will stay in the archives until you delete them.

Permanent? Temporary? What's that all about?

When someone submits a post, be it a partner or regular poster, they have the option to select whether their pic is permanent or temporary. Permanent pics are those that will exist on the submitter's server for many weeks or months. This means that once they reach the end of their life in the current database they will be placed in the archives. If the submitter indicates it is a temporary pic, it will not be placed in the archives once it reaches the end of it's life in the current database.


Through the admin.cgi script you will have complete control over your picpost. This is where you will moderate posts, view reports of cheaters or dead links, update the HTML for your picpost pages, and manage many other things.

Approving and rejecting posts in the queue is one of the major tasks you will have to do for your picpost. You can easily view all of the posts in that database and decide if you want to add them or delete them. If you choose to reject them, there is the option to choose a rejection e-mail to send them. This will only be sent if you choose something other than 'None' and the submitter has selected to be notified. You can add as many custom rejection e-mails as you like, so each situation can have it's own message. More information on editing the rejection e-mails can be found in templates.html

If you are approving posts, you can ignore the rejection e-mail field. The user will be sent the e-mail message from _email_approved.etmpl if they selected to be notified of their post's status. This is a generic e-mail and is sent to all approved posts, however it can be customized to fit your site.

The Blacklist

The blacklist is a list of items that you do not want to be posted to your picpsot. There is a blacklist for e-mail addresses, URLs, and words. If you have found that someone is posting bogus pics, you can blacklist their URL or e-mail address. If there are certain words that you do not want to appear on your site, you can ban those from the pic and site descriptions.

With the e-mail and URL bans, it is possible to block an entire domain, or an exact URL or address. For example, if you want to ban all people using Hotmail e-mail addresses from posting, you should add '' to the e-mail blacklist. If you only want to ban John Doe, you would add '' to the blacklist - this will allow others from to continue posting.

Reciprocal Links

If you are going to require reciprocal links, you will need to setup at least one valid linking syntax before people will be able to submit their pics. This is done through the admininstrative script, and you can use any HTML you want except a textarea tag. Obviously, once you enter some valid linking syntax in the administrative script, you will want webmasters to know what it is. You will need to edit the _post_main.htmlt template to insert the valid linking code.

You can enter any number of valid reciprocal links. When a user makes a post, their site only needs to have one of those valid links on their site. If the script doesn't find any valid reciprocal links, it will instantly reject the post and inform the poster that they need to add a link.

Naming of Category Ranking Pages

Each of your category archive pages will be named based on the category and file extension entered in setup.cgi. The software will take the category name, replace all non-alphanumeric characers with an underscore, make all letters lowercase, and attach the file extension. We'll give a few examples so you can see how they will be named. In these examples, we will assume 'html' was entered for the file extension in setup.cgi.
Category         HTML Name
--------         ---------
Internet         internet.html
CGI Scripts      cgi_scripts.html
Unix/Linux       unix_linux.html