World Wide Classifieds Merchant Version 2.0 by World Wide Creations (TM) Copyright ©2000 World Wide Creations All Rights Reserved As part of the installation process, you will be asked to accept the terms of this Agreement. This Agreement is a legal contract, which specifies the terms of the license and warranty limitation between you and World Wide Creations and World Wide Classifieds. You should carefully read the following terms and conditions before installing or using this software. Unless you have a different license agreement obtained from World Wide Creations, installation or use of this software indicates your acceptance of the license and warranty limitation terms contained in this Agreement. If you do not agree to the terms of this Agreement, promptly delete and destroy all copies of the Software. VERSIONS OF SOFTWARE ----------------------------------------------------------------------- Only one copy of the registered version of The World Wide Classifieds may used on one web site owned by one owner or an entity. LICENSE TO REDISTRIBUTE ----------------------------------------------------------------------- Distributing the software and/or documentation with other products (Commercial or otherwise) or by other than electronic means without World Wide Creations prior written permission is forbidden. All rights to the World Wide Classifieds software and documentation not expressly granted under this Agreement are reserved to World Wide Creations. DISCLAIMER OR WARRANTY ----------------------------------------------------------------------- THIS SOFTWARE AND ACCOMPANYING DOCUMENTATION ARE PROVIDED "AS IS" AND WITHOUT WARRANTIES AS TO PERFORMANCE OF MERCHANTABILITY OR ANY OTHER WARRANTIES WHETHER EXPRESSED OR IMPLIED. BECAUSE OF THE VARIOUS HARDWARE AND SOFTWARE ENVIRONMENTS INTO WHICH THE WORLD WIDE CLASSIFIEDS MAY BE USED, NO WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE IS OFFERED. THE USER MUST ASSUME THE ENTIRE RISK OF USING THIS PROGRAM. ANY LIABILITY OF WORLD WIDE CREATIONS WILL BE LIMITED EXCLUSIVELY TO PRODUCT REPLACEMENT OR REFUND OF PURCHASE PRICE. IN NO CASE SHALL WORLD WIDE CREATIONS BE LIABLE FOR ANY INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES OR LOSS, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR THE INABILITY TO USE EQUIPMENT OR ACCESS DATA, WHETHER SUCH DAMAGES ARE BASED UPON A BREACH OF EXPRESS OR IMPLIED WARRANTIES, BREACH OF CONTRACT, NEGLIGENCE, STRICT TORT, OR ANY OTHER LEGAL THEORY. THIS IS TRUE EVEN IF WORLD WIDE CREATIONS IS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO CASE WILL WORLD WIDE CREATIONS'S LIABILITY EXCEED THE AMOUNT OF THE LICENSE FEE ACTUALLY PAID BY LICENSEE TO WORLD WIDE CREATIONS. ---------------------------------------------------------------------------------- The World Wide Classifieds 2.0 by www.worldwidecreations.com ------------------------------------------------------------- In the WinZip file you will find all the .pl and .cgi and .lib and .gif files plus another WinZip file with all the .pm files. INSTALLATION ------------ Connect to your server and create a folder (directory) inside the cgi-bin (or equivelent) for the classifieds script. INSIDE this folder, create THREE more folders named "categories" "templates" "database" "temp". (Note: do not use the quotes in the name) CHMOD these folders 777 (readable writable executable). Now go to a web accessible section of your server (for example, where you store webpages/graphics) and create a folder called userpics and CHMOD this folder 777. UPLOAD the pic.gif file here in BINARY mode. Then switch your FTP program BACK to ASCII. Open every .cgi (and upload.pl) file that came with the Winzip file and change your path to Perl to reflect your server. This is generally #!/usr/bin/perl If you are unsure, check your server documentation. Save all the .cgi files. Upload all the .cgi and .pl and .lib files to the folder you created in the cgi-bin for the classifieds IN ASCII MODE - VERY IMPORTANT! If you upload in Binary more you will get an Internal Server Error. Make sure you FTP program is NOT set on automatic, as many will upload the cookie.lib in BINARY when it should be in ASCII. CHMOD all of these files 755. Unzip the pm files and open the folder called "templates" and upload all the files in there. CHMOD all of these files 777. Open the setup.pl file. Define the following variables: $classurl - This is the COMPLETE URL to the classads.cgi script. $basepath - THIS CANNOT BE STRESSED enough: THIS IS THE MOST IMPORTANT VARIABLE! If you do not define this variable correctly, you will encounter a plethora of errors. This is your ABSOLUTE path to the script. Your server documentation should tell you what your path is to your cgi-bin, for example /home/joeuser/cgi-bin would translate to /home/joeuser/cgi-bin/classfolder providing you named the classifieds folder classfolder. DO NOT include a trailing slash. AGAIN do NOT include a trailing slash. There are astronomical amounts of warnings we can give you about this variable; suffice it to say that 95% of all installation problems are due to this variable being incorrect. You can run the script called basepath.cgi and most of the time it will report the correct basepath to you via your browser. Just upload it to the directory where you plan on installing the classifieds, CHMOD it 755 and call it from your browser. For example: http://www.yourserver.com/cgi-bin/classifieds/basepath.cgi $uploadurl - This is the COMPLETE URL to the upload.pl. upload.pl should be placed in the same folder as the classads.cgi. $filelimit - Is the file size (in K) maximum that you will allow a user to upload at a time. Default is 25K $adminpass - This is your administrator password. $amountpics - This is the limit of how many pics a user may have stored on your server at one time. Default is 5 $picurlpath - This is the INCOMPLETE URL to the userpics folder. DO NOT USE HTTP:// just the domain and directory. $picdir - Again, this is a VERY important variable. If this is not correct, users will not be able to upload pics to their picfolder. In fact, no folder will be created for them to do so, and you will get an error when they attempt to upload a file. The users file is created upon registration, so if you do this incorrectly the first time, you will have to re-register a user to see if you indeed did it correctly. This is the ABSOLUTE PATH to the userpics directory and DOES NOT INCLUDE THE TRAILING SLASH. AGAIN does NOT include. %category - This is where you define the categories and sub categories. The first line for example shows the key: "toys" this will be the folder that is created for the MAIN category. The value for toys is: 'Toys, Beany Babies, Antique, Models', The first value is the name of the main category (Toys) the other values (after the first comma) are the subcategory of Toys. A comma separates each category. (do not put a comma after the last subcategory) Do not use any special characters like & or @ or | or any other Perl function as this may create unusual things. Just use letters and/or numbers. Here is an example below: %category = ( toys => 'Toys, Beany Babies, Antique, Models', applian => 'Appliances, Refrigerators, Stoves, Other', elect => 'Electronics, Home, Entertainment, Other', comput => 'Computers, Equipment, Desktops, Laptops', furn => 'Furniture, Wooden, Plastic, Outdoor', home => 'Home And Garden, Rakes, Tarps, Lawn Mowers', help => 'Help Wanted, Business, Labor, Other', other => 'Other', ); $picimage - This is the COMPLETE URL to the pic.gif file, which should be in the userpics folder (upload it in BINARY mode) $maxpost - This defines the maximum amount of ad's any user can post. $adexpire - This is how many days until an ad expires and is killed. $filelock - Leave this as one unless for some reason your server does not allow file locking $mailserver - This is your path to sendmail, check your server documentation for more information . @CENSORED - These are words that you may wish to censor from ad's. Make sure you follow the delimination. ---------------------------------------- ClickBank Setup ---------------------------------------- Clickbank is one of the greatest services on the Internet! You can setup affiliate programs and find many other ways to accumulate cash. World Wide Creations has used clickbank for quite some time and have been very happy with their service. No MERCHANT account needed. Please refer to clickbank.com for more information. Before we go any further lets explain the Clickbank concept. Basically when someone clicks a Clickbank link that you setup, the user goes to the Clickbank payment page and enters their credit card info, Clickbank then redirects them to the link you specify in your account setup. When you setup the Clickbank link make sure it points to the URL to your DOWN.CGI script NOT THE CLASSADS.CGI! Very important! So a link to the down.cgi might look something like: http://www.yourserver.com/cgi-bin/classfolder/down.cgi You have to enter a purchase validation key in the modify your accounts settings on Clickbank.com. This is used for the down script to validate that someone did indeed purchase the ad. YOU WILL HAVE TO DEFINE THIS KEY IN THE DOWN.CGI FILE!! You will see it in the down.cgi script here: ############################### $a="Your_Secret_Key_Here"; ############################### Once the down.cgi script validates the user did purchase the ad, it posts the ad. Do not forget to set the path to Perl in the down.cgi script. Once you finish editing the down.cgi script upload it into the same directory as the classads.cgi and CHMOD it 755. Back to the setup.pl file. Now the next variable is DIRECTLY related to your merchant capabilities: $click is the CLICKBANK LINK. Make sure you setup the purchase validation key in your account at clickbank.com. So basically all you have to change here is enter your clickbank name where it says username in the variable and the number between username and test is the link number you see associated in your account on clickbank. The same number you have for the clickbank link to the down.cgi file NO SPACES! MAKE SURE YOU TEST THE SCRIPT FIRST!! Do not immediately start charging your users until you are sure you installed this correctly. -------------------------------------------------------------------------------------------------- Save and close the setup.pl file. Upload in ASCII it to the same folder as the classads.cgi resides. CHMOD 755. Call the script via your browser, for example: http://www.yourserver.com/cgi-bin/classfolder/classads.cgi. CLICK categories. This SHOULD have created all the necessary database files. You can check by opening the database folder (you may have to refresh) and there should be .dat files in there. Also, inside the categories folder should be .dat files and also folders. The script should now be ready to go. ADMINISTRATION -------------- Your Admin username is Admin and your password is defined in the setup file. Admin is hard coded into the script and should not be changed! You activate admin functions by calling it in your browser, for example: http://www.yourserver.com/cgi-bin/classfolder/admin.cgi TEMPLATE MODIFICATIONS ---------------------- It is recommended that you modify the template files via a text editor, but the admin script allows you to do so via the web. BACKUP ALL template files before editing them! Headers - We did not create a header template, but you can include headers in each template by pasting the code into the template. DO NOT USE HEAD TAGS in the templates, as this may affect the cookies operation. COOKIES MUST BE USED. Once the user closes their browser, the session is over and the cookie is dead. Virus's CANNOT be transferred via a cookie. Cookies CANNOT be executed, they are just text files. Do not remove the tags in the templates that look like . This is where the said value will be placed. You can move it if you would like, but we do not recommend deleting or altering them. SECURITY -------- If you wish to be ultra secure with your administration functions, make the admin.cgi script non-executable via CHMOD until you need it. Either way, the Admin script is very secure. UPGRADING FROM 1.0 ------------------ If you are upgrading from version 1.0 you can import your current registrations to the new script by uploading the convert.cgi script into the directory where your classads.cgi 1.0 is currently stored. Define the basepath (without the slash) and the regdir and execute the file. If all goes well it should create a file called reg.dat. Place this in the database folder and it should act as your reg database file. SUPPORT ------- You can receive support in our forum at www.worldwidecreations.com