™| The Configuration File (config.txt) is the brains behind the running of a site utilizing FlyPage. In this file all the particulars for the overall site operation plus all the individual FlyPages are defined. Below we have included a snap shot of a config.txt file and have documented what each line does and the format it must follow. The red numbers are for reference and are not to be included in the config.txt file. |
|
ITEM #1 - Website url - This is the actual home page of the web site that FlyPage is installed into. This will be used on the editing pages to link/send the FlyPage content editor (person) back to their site. ITEM #2 - Website Title - This is the link title that is used for Item #1 ITEM #3 - Developer - This is the name of the developer of the site that is responsible for helping out the FlyPage content editor (person) if they need any assistance in the day to day use of their site. It is for reference only. ITEM #4 - Developer E-Mail - This becomes the active link with item #3. This makes it easy for the FlyPage content editor (person) to contact the Developer. ITEM #5 - Developer Phone - Just reference for Item #3 ITEM #6 - License - This is the registered license code number given to the purchaser of FlyPage. This is issued out by Web Marketing Services, Inc.. Without a proper license code use of the product would be illegal and the program will not function properly. ITEM #7 - Page - This is the title of the webpage that will be using FlyPage Tags. This name should be easily recognizable to the FlyPage content editor (person). It is what will appear on the FlyPage Editor. ITEM #8 - Page Path - This is the actual path on the web server to the webpage that will be using the FlyPage Tags. It must be the full path as it tells the FlyPage program where to find the webpage. ITEM #9 - Page Template - This is the template page (text file) which holds the default values for all the FlyPage Tags on this webpage. It is where the program finds the actual content to reload onto the page if the FlyPage content editor (person) selects "REVERT TO ORIGINAL" during the edit process. This feature of the FlyPage system is for "just in case" anything gets totally screwed up the FlyPage content editor (person) can always get the page back to how the developer designed the page in the first place. ITEM #10 - Page URL - This is the actual url of the webpage that contains the FlyPage Tags. It must be a full url starting with "http://". This url will be used in a link to review the page during the editing process. ITEM #10-A - urlblock - This is to block all url's in the standard flypage tag. It will replace any web site url with xxx.xxxxxx.xxx. This is a feature that 99.9% of the users will set to "off". To activate it make this variable "on" ITEM #11 - Username - This is the username|password combination that will be needed to be able to access the FlyPage Editor to update the content on this page. ITEM #12 - Username (2) - Each page can have as many username|password combinations as needed. This feature of FlyPage allows the developer to grant editing/access privileges to as many people as necessary. When a username|password is entered into the FlyPage logon screen all the pages that have the matching username|passwords will be included in a drop down selection box. ITEM #13 - FlyPage Tags Definitions - These are the identifier names of the FlyPage Tags that are being incorporated into this webpage. The tags must be in sequential order beginning with v001. There can be any number of tags associated with a single FlyPage. The text information associated with each tag is the instructions that the FlyPage content editor (person) will see next to the editing box for that Tag. This text instruction can be as long as needed to clearly instruct the user what to incorporate into the content of that tag's editing box. HTML can be used with this text. The clearer the instructions are here (by the developer) the easier the process will be for the FlyPage content editor (person). NEW FEATURE ADDED IN FLYPAGE UPDATER 2.02 (May 17th, 1999): With the standard flypage tag you now can set the maximum number of characters allowed to be shown on the web page. You also can set if HTML will be allowed with this flypage tag. Both these new features are on a tag by tag basis. The proper format is the following: v007=text description goes here as usual|1000|NOHTML This above example limits the "shown" content to be 1000 total characters and no html will be allowed. HTML tags are converted to text on the resulting html page instead of being processed. v007=text description goes here as usual|NOHTML In the above example the input length is unlimited but is still limited to plain text: This following will *not* work because the size limit must be listed first before the NOHTML. v007=text description goes here as usual|NOHTML|1000 The default ( NO number or NOHTML is left off the tag information) is that the user has options of both 'plain text' and 'html' with an unlimited char length. One drawback is that the user can type as much as they want but it will be chopped off it the maxlength is set. HTML scrolling textboxes do not offer a maxlength option like single line text boxes. IMPORTANT NOTES - Items #7 - #13 need to be repeated for each additional webpage that will incorporate FlyPage Tags. Each webpage will need to have its own section (make sure there is one blank line between sections) with Items #7 - #13 included. Items #1 - #6 will only appear once in the config.txt file. The config.txt file must always be transferred (FTP) as ASCII format to preserve the formatting structure whenever you are moving it from your pc to your website. Any text editor or word process can be used to create this file. You may just want to edit the sample config.txt file supplied. |