Unix Installation Instructions
If you need assistance with this software you must use the resources in the CGI Works owners lounge. See the
bottom of this file for more details on obtaining technical support.
- At this point it is assumed you have extracted the archive containing AutoPost Pro Pro. If you have not yet done so,
you should do that now.
- Now you will want to locate Perl 5 on your server. If you are not sure where to find it, contact your server
administrator and ask them. Generally it can be found at /usr/bin/perl or /usr/local/bin/perl
- If Perl 5 is located at /usr/bin/perl on your server, you may skip this step. If it is not, you will need to
open each of the .cgi files in a text editor such as Notepad. Change the first line of each file to point to Perl
5 on your server. For example, if Perl 5 is at /usr/local/bin/perl, then the first line will be #!/usr/local/bin/perl
- You will now need to login to your server and create some directories for AutoPost Pro Pro. First off, decide where you
want the .cgi files installed. Generally it is a good idea to keep them in a cgi-bin (or equivalent) directory. Once
you have decided where you want the .cgi files, change into that directory. Inside that directory you will need to create
3 subdirectories; name them templates, data, and admin. Note: The only files you should place in these directories are the
ones indicated in this documentation. Uploading other files can and will cause problems.
Now, you need to decide where you want the HTML files written to. This will need to be outside of the cgi-bin directory.
Once you have decided where you want them to go, record that information for later use.
Example Directory Structure:
||location of post.cgi and app.pl files
||location of admin.cgi and setup.cgi files
||location of script data files
||location of all template files
||where the main HTML files will be generated
- Next, you need to open cgiworks.pm in a text editor and change two of the variables. Locate the lines indicated below:
$DDIR = '/mnt/web/guide/cgi/cgibin/app/data';
$TDIR = '/mnt/web/guide/cgi/cgibin/app/templates';
You will need to change the two values in quotes to values that match your system. The $DDIR variable needs to be set to the
full path to the data directory, and the $TDIR variable needs to be set to the full path to the templates directory. Using the
example directory structure above, those two lines would look like the following:
$DDIR = '/home/username/cgi-bin/picpost/data';
$TDIR = '/home/username/cgi-bin/picpost/templates';
If you would like the script to keep a log of fatal errors it encounters (this can be useful in tracking down problems should
they arise), you will need to set the $ERRLOG variable in cgiworks.pm. All you need to do is change the 0 to a 1.
Once you have finished making those changes, save cgiworks.pm. You now need to edit the .htaccess file from the admin directory
of the archive. This is the file that will enable the password protection of the admin directory once it is on your server. A
description of what needs to be edited and how to do it can be found in the .htaccess file. This file should be edited in a text
- Now you are ready to begin uploading the files to your server. VERY IMPORTANT: You must upload ALL of
the AutoPost Pro Pro files in ASCII mode, or it will not function properly. If you are not sure how to do this, consult the
documentation for your FTP client. If you get a Script Error message saying you may not have stripped the carriage returns,
this means you did not upload all the files in ASCII mode - try again.
Below is a table of where each file should be uploaded, using the example directory structure above:
All .htmlt and .etmpl files
- Next, you will need to set permissions on the files and directories that AutoPost Pro Pro will be using. If you are not
sure how to set permissions, consult the documentation for your FTP client and/or contact your server administrator for
more information. Below is a table containing the permissions you will need to set on each file.
|File or Directory
|All .cgi Files
|All .htmlt & .etmpl Files
|Directory where HTML files will be written
These are only the recommended file permissions, and may need to be altered depending on your
server configuration. Once you have all permissions set, continue to the next step.
- You are now ready to begin the WWW based portion of the setup. In your browser, type in
the full URL to the init.cgi file on your server. This will initialize the installation, and
prepare the administrative directory. Once you have run init.cgi, and received a message indicating
you may proceed, you can bring up setup.cgi in your browser. It is also now safe to remove the init.cgi
file from your server - it is no longer needed. The default login info to access the
password protected administrative area is:
You will then be presented with a page where you will fill in variables and options for the software.
After you have set all of the variables, click the button near the bottom of the page.
If everything went well, you will be presented with a page telling you that the variables have been
recorded, and some self tests will be done by the script. If all the tests pass, you are ready to go
on. If any of them fail, you will need to check file permissions and directory settings. If you get
any CGI error messages after you press the button, you most likely have either a permissions setting wrong
or one of the variables in cgiworks.pm is incorrectly set.
- You should now be ready to begin using the software. The first thing you will want to do is
point your browser to admin.cgi. Use the same login information as is listed above. The 'admin'
username is the superuser for this software. When you are logged in as that user you have permission
to execute all functions the administrative script has.
Once inside the admin script you can start exploring the features, but make sure that you change the superuser
password soon after your initial installation. In the administrative script, you will find links to
"help" near the bottom of each page. Clicking on that help link will bring up a description of the
function you are working with
After Installation Is Complete
Once you have completed the installation you will want to get your picpost setup and ready
to accept new posts. Here we will outline the steps you will want to take immediately
following the installation. You should also begin reading the overview.html documentation
file so you can get an understanding of how the software works.
- The first thing you will want to do is setup the HTML for each of your picpost
pages. This is done through the administrative script by using the "Edit HTML For" function.
This is the third function listed on the main page of the administrative interface.
Editing the header/footer
Editing the header and footer for your main picpost page will setup the HTML that appears
above and below the listing of posts. All HTML entered in the header will appear above the posts; all
HTML entered in the footer will appear below the posts. Any HTML you want can be entered here,
with the exception of a textarea tag. Typically your header will contain the opening html, title, and
body tags, as well as a link to post.cgi so webmasters can add their posts. You will need to add
links to your archive pages here as well. Each category you enter in setup.cgi will have an archive
The header and footer do contain some template values. More information about setting these up is found in the
templates.html file. See the portion labled "Edit HTML For [page]" template in admin.cgi
Editing the HTML template
A complete description on how to generate your template can be found in the template.html
documentation file. There is also some additional information in templates.html
which reinforces what was explained in the template.html file. We will briefly discuss it here as well.
The template allows you to insert your own style of how to list the posts. In the template form,
you will enter the HTML that will be used for a SINGLE posting. The script will then use that HTML
for each of the posts in your database. For most applications, each of the template variables should only
appear ONCE in the template. If you find yourself inserting #%GURL%#, #%DESC%#, or any of the script
values more than once in the template, you are most likely doing something wrong.
- After HTML is setup for all of your picpost pages, you can use the Rebuild Main Page and Rebuild
Archives functions. Do this from the administrative script. They are the first and second functions available from
the first pull down menu. Note that you should always let the script create the html files.
If they already exist on the server, you should delete them before rebuilding the pages for the first time. Once
you have successfully rebuilt the pages, you can view the output on the HTML files you selected
to have the galleries written to - there is a link on your administrative page to the main picpost HTML file.
- The next thing you will probably want to do is edit the templates for the post.cgi and partner.cgi
scripts. These are all located in the templates directory, and can be edited with any HTML editor.
Each of the files contains normal HTML, and special items that the script recognizes. The special
values that the script understands are surrounded by #%%#. You should never edit those values; you
can move them around all you want, but don't change anything between the #%%#. Complete descriptions
of each of the templates can be found on templates.html which is available
from the owners lounge.
Getting Help From CGI Works
Where To Go To Get Tech Support
If you need any assistance with this software, you must use the resources in the CGI Works owners lounge.
This is the only way to contact the tech support department. Use the following URL, and the login information
you selected when you purchased the software:
Important Tech Support Notes:
If you edit the scripts in any way other than described above, you will no longer be eligible for technical support.
We absolutely cannot provide support for edited copies of our software.
The only way we provide support for our commercial scripts is through the owners lounge.
We do it this way to make sure we are providing support only to those who have paid
for the scripts and deserve it. If you post a message at the Freeware Help Board
it will not be deleted - you must post on the Owners Lounge board. Also, sending
a plain e-mail to us will be ignored, you must use the tech support request form in the
These methods also help to ensure that we are not wasting our time providing
support for illegal copies of our software, and will result in faster responses
to legitimate owners questions.
Thank You, and enjoy your new script!