ZISP Demon Logo
 

[ IDs - Reference ]

Using IDs allows you to use the same Dynamic Tools many times on your website

When do you need to use IDs?

You might want to use the same dynamic tools several times on your website. For example, you could place a guest counter on every page of your website, or have two discussion boards (one for fishing, and one for snowboarding).

Without distinguishing the tools with IDs, they would interfere with each other. All your counters would use the same "count.txt" file to store their values. Your two discussion boards would use the same data directories and templates, and would be indistinguishable from each other.

With IDs, your counters can each have their own file to store their values, so they won't interfere with each other. Your discussion forums can have their own data directories and templates.

What does an ID look like?

An ID has a value. Usually, it's best to let the value be a number between 0 and 99, but you can use any two characters or digits.

Every time you make a link to a dynamic tool, you must specify an ID value. For example, to create a guest counter with an ID of "45", use:

<IMG SRC="/zisp/counter?ID=45">

The dynamic tool appends the ID to the name of any data files it uses. So, the Guest Counter usually stores its value in a file called "count.txt", but this one will store its value in "count45.txt".

The standard data file will be created automatically on first use, however each of these extra ID files must be created by you and uploaded to your webiste before they can be used. This can be acheived using a simple text editor like Notepad, and your ISP should provide details of how to place files in your website. This is mainly to stop users of your site from arbitrarily creating extra counters, discussion forums, etc, and generally filling up your web space with files that you don't need.

Templates Example

IDs are also used when the Dynamic Tool looks in your "easyzisp" folder for its template files (see the Templates Reference for more information on templates.).

For example, suppose you have two discussion forums (IDs of "45" and "46"). The discussion forum with ID "45" will store its data in a folder called "forum45", and look for templates called "<template-name>45.html".

If these templates are not present, it will fall back to the system default templates.