Location: PHPKode > projects > Article Manager > pm30/cgi/data/config/docs.xml
#---------------------------------------------------------
<description variable="base" topic="database">
Define database fields
</description>

<documentation variable="base">

 Database Initilization
 <p>
 To enable a field in the database you need to put it into this list.
 Make sure to put comma between fields.
 <p>
 This will create the database, if you want to add
 a new field after the database is already created, add the field
 to the end of the list, if you add to middle, you might mess
 up the database. Try to spend some time on thinking about
 fields of your database, before filling this out.
 <p>
 When you want to use a field in a page, you will use these
 names to retrieve them, for example, %%name%% will retrieve
 the 'name' field of the profile. But don't use more fields
 than you actually need, unnecessary field means waste of resources
 (hard disk space, ram) and speed.
 <p>
 If the field is multiple-words put into 'quotes'.
 <p>
 Do not remove the first 3 fields:
 <br>
 ---   login, ID, password,

 <br>
 <br>
 You can remove the next 6 fields, but if you don't,
 they will be automatically filled by the script, so you
 don't need to include them in your forms:
 <br>
 ---   update_time, register_time,
 <br>
 ---   IP, sortable_register_date, sortable_update_date, mailing,
 <br>

</documentation>



#---------------------------------------------------------
<description variable="base_descriptions" topic="database">
Database Field Descriptions
</description>

<documentation variable="base_descriptions">
These variables are useful for database wizard. So that it can 
create registration and modification forms.
</documentation>


#---------------------------------------------------------
<description variable="not_null" topic="database">
Required database fields
</description>

<documentation variable="not_null">
 These are required database fields.
 <li> If one of these fields are missing on registration, the script will give error message.
 <li> If one of these fields are missing on modification, the script will keep the old data for the field.

 These fields must be in <variable>base</variable> variable.
</documentation>

#---------------------------------------------------------
<description variable="template_rules" topic="templates">
Template Rules
</description>

<documentation variable="not_null">
These rules tell the script how to behave. You can use them to disable things. Or you may use 
them to implement multiple membership types
</documentation>

#---------------------------------------------------------
<description variable="multiselection" topic="database">
Fields including multiple data
</description>

<documentation variable="multiselection">
These fields support multiple data selection using a select HTML select form field.
For instance, if you make "state" as a multiselection field, someone can select  both "New York" 
and "California". This is a new feature, so it may not work perfectly.
<p>
Format: 'fieldname'   => 'no of allowed selections'
<br>
<li><i>fieldname</i> should be a field in the @base array
<li><i>no of allowed selections</i> define how many options can be selected at maximum.
</documentation>

#---------------------------------------------------------
<description variable="auto_link" topic="database">
Hyper linkable fields
</description>

<documentation variable="auto_link">
List all of the fields that may include URLs 
that needs to be turned into a clickable links.
<p>
Do not use this to link email and homepage fields, 
instead create your own links for them, such as 
&lt;a href=%%homepage%%&gt;%%homepage%%&lt;/a&gt;. This is useful for 
text fields that may include URLs in them. 

<p>Such as a "news" field like this:
<br>
<font color=gray>
<i>Hi people, this is a great site: 
http://www.interlogy.com</i>
</font>
<br>
Will be turned into this:
<br>
<font color=gray>
<i>Hi people, this is a great site: 
&lt;a href=http://www.interlogy.com&gt;http://www.interlogy.com&lt;/a&gt;</i>
</font>
</documentation>

#---------------------------------------------------------
<description variable="default" topic="database">
Default values for data
</description>

<documentation variable="default">
If a database field or a tag is not defined, then the default views entered 
here will be showed to the user.
</documentation>

#---------------------------------------------------------
<description variable="reserve_logins" topic="database">
Reserved Login Names
</description>

<documentation variable="reserve_logins">
You can reserve login names using this feature. Simple list all login 
names with a comma. If a user tries to create an account with the same 
login name defined here, he/she will get an error and will fail to create 
an account with that login name.
<p>
You can use this feature to disable users from damaging your files. 
For instance, (not recommended) you are letting your users create 
accounts such as http://www.domain.com/loginname, and your "images" 
directory is located at http://www.domain.com/images. It might be possible 
for someone to create an account with login name "images", and delete your 
images directory by simply deleting their account. If you are sharing your 
static profile directory with other directories, you must define these 
directories in the "Reserved Logins" list.
</documentation>

#---------------------------------------------------------
<description variable="send_confirmation" topic="email">
Send registration confirmation email?
</description>

<documentation variable="send_confirmation">
If you would like the script to send a confirmation email 
after registration, select yes. 
</documentation>

#---------------------------------------------------------
<description variable="mail_method" topic="email">
Define how to send emails
</description>

<documentation variable="mail_method">
It should be set to <i>sendmail</i> or <i>SMTP</i>.
<br>
Sendmail is the recommended method to send emails. However 
if you server is not UNIX based, then you may not have sendmail 
installed. 
</documentation>

#---------------------------------------------------------
<description variable="sendmail" topic="email">
Location of sendmail
</description>

<documentation variable="sendmail">
If you have selected sendmail as your <variable>mail_method</variable>,
then you must set this field correctly. 
<p>
This field should be an executable location like <i>/usr/sbin/sendmail</i>.
<p>
If you don't know the location of sendmail, you may either use "whereis_sendmail.cgi"
script until utils directory, or you may ask your hosting provider.
</documentation>

#---------------------------------------------------------
<description variable="smtp_server" topic="email">
Hostname of SMTP
</description>

<documentation variable="smtp_server">
If you have selected SMTP as your <variable>mail_method</variable>,
then you must set this field correctly.  
<p>
This field should be a hostname like <i>smtp.domain.com</i>.
<p>
If you don't know the hostname for you SMTP, you may try smtp.yourdomainhere.com 
or you may ask your hosting company.
</documentation>

#---------------------------------------------------------
<description variable="from" topic="email">
From E-mail address
</description>

<documentation variable="from">
The email address that will be placed in the "From:" field of the emails.
</documentation>

#---------------------------------------------------------
<description variable="confirm" topic="email">
Customize registration confirmation email
</description>

<documentation variable="confirm">
Set title and body of the confirmation email.
</documentation>

#---------------------------------------------------------
<description variable="subject_lost_password" topic="email">
Lost password email subject
</description>

<documentation variable="subject_lost_password">
Lost password email subject.
</documentation>

#---------------------------------------------------------
<description variable="notify_emails" topic="email">
Notify about the changes on profiles
</description>

<documentation variable="notify_emails">
If someone modifies or deletes their account. An email will be sent 
to the defined email addresses.
<p>
<li>You must quote emails with single quotes.
<li>You must have comma between address if you define more than one address.
<br>
'hide@address.com', 'hide@address.com'
</documentation>

#---------------------------------------------------------
<description variable="check_email" topic="email">
Check email formats
</description>

<documentation variable="check_email">
Should the email formats be checked in the registration?
</documentation>

#---------------------------------------------------------
<description variable="send_randompassword" topic="email">
Email random password on registration
</description>

<documentation variable="send_randompassword">
Should a random password be sent to the user after registration?
<p>
If you select this as "no", then you must define password fields 
in the registration form. Add these to the registration:
<p><i>
Password: &lt;input type=password size=30 name=password1&gt;
<br>
Password again: &lt;input type=password size=30 name=password2&gt;
</i>
</documentation>

#---------------------------------------------------------
<description variable="profile_email_subject" topic="email">
Subject for email sent from profile page
</description>

<documentation variable="profile_email_subject">
 Set the subject of the email that can be sent from profile
<p>
 If you leave it empty, you can let users to enter a
 subject by adding this line:
 <p><i>
 &lt;input type=text size=20 name=subject&gt;
 </i>
</documentation>

#---------------------------------------------------------
<description variable="profile_email_header" topic="email">
Header for email sent from profile page
</description>

<documentation variable="profile_email_header">
The Header of the email body that can be sent from profile.
The text you enter here will be placed to the top of the emails.
</documentation>

#---------------------------------------------------------
<description variable="profile_email_footer" topic="email">
Footer for email sent from profile page
</description>

<documentation variable="profile_email_footer">
The Footer of the email body that can be sent from profile.
The text you enter here will be placed to the bottom of the emails.
</documentation>

#---------------------------------------------------------
<description variable="set_return_path" topic="email">
Set return path?
</description>

<documentation variable="set_return_path">
 Note that this is not something you need to set.
 Everything will work fine. Receivers can still reply to the
 emails. This is useful for getting bounced emails.
</documentation>

#---------------------------------------------------------
<description variable="confirm_approval" topic="email">
Approval message contents.
</description>

<documentation variable="confirm_approval">
When a user is approved, an email will be sent. 
You can customize this email.
</documentation>

#---------------------------------------------------------
<description variable="base_image" topic="upload">
Define uploadable image fields.
</description>

<documentation variable="base_image">
 This hash defines the uploadable image fields. 
 <br>
 the fields on the left must be  a database field and 
 it must be in base fields list.
 <br>
 the fields on the right are the captions for the upload page
</documentation>

#---------------------------------------------------------
<description variable="imagesdir" topic="files and directories">
Image Directory Path
</description>

<documentation variable="imagesdir">
This variable defines the image directory path on the server. 
For instance: 
<br>
On unix: <i>/home/yourdomain/public_html/images/</i> 
<br>
On windows <i>C:/webserver/folder/images/</i>. 
<p>On windows, do not use backslash(\), use slash(/) instead. 
<p>
You should have a slash at the end.
</documentation>

#---------------------------------------------------------
<description variable="imageswww" topic="files and directories">
URL for the Images
</description>

<documentation variable="imageswww">
Use a URL like
 "http://www.yourdomain.com/pmpre/images/"
 or a path like "/pmpre/images/"
<p>
You should have a slash at the end.
</documentation>

#---------------------------------------------------------
<description variable="any_extension" topic="upload">
Upload allow all file types?
</description>

<documentation variable="any_extension">
Do you wish to allow all file types?
<p>
If no, only the defined extension types will be 
allowed to be uploaded.
</documentation>

#---------------------------------------------------------
<description variable="ext" topic="upload">
Upload allow files extensions
</description>

<documentation variable="ext">
List the allowed file extensions.
</documentation>

#---------------------------------------------------------
<description variable="max_upload" topic="upload">
Maxiumum file size of upload(KB)
</description>

<documentation variable="max_upload">
Type the maximum size of an uploadable image.
<br>
It should be in Kilobytes. For instance type 100 for 100 KB.
</documentation>

#---------------------------------------------------------
<description variable="image_thumbs" topic="upload">
Make thumbnails of uploaded images? (ImageMagick required)
</description>

<documentation variable="image_thumbs">
 You need to have imagemagick in your server to use
 this features. Read utils/thumb_annotate_image/readme.txt
 for further instructions to enable these features.
 This feature had to be disabled by default because most of the
 the web hosts do not have imagemagick installed by default.
 <p>
 To call a thumbnailed image on any template, use %%THUMB:images1%% 
 kind of tags.
</documentation>

#---------------------------------------------------------
<description variable="image_thumb_width" topic="upload">
Width of the thumbnailed images?
</description>

<documentation variable="image_thumb_width">
This will help you set the width pixels for the generated thumbnails.
The height of a thumbnail will be defined according to the image's
size ratio. For instance, if the image is 400x600 in widthxheight 
ratio and if you set width as "200" here, then the new size of the thumbnail
will be 200x300.
<p>
To call a thumbnail of an image on any template, use %%THUMB:image1%% 
 tag.
</documentation>

#---------------------------------------------------------
<description variable="image_scale" topic="upload">
Scale large uploaded images? (ImageMagick required)
</description>

<documentation variable="image_scale">
 You need to have imagemagick in your server to use
 this features. This feature had to be disabled by default because most of the
 the web hosts do not have imagemagick installed by default.
 <p>
 If enabled this feature will resize an uploaded image if it is too large.
</documentation>

#---------------------------------------------------------
<description variable="image_max_width" topic="upload">
Width for scaled images? 
</description>

<documentation variable="image_max_width">
This will help you set maximum width pixels for uploaded images.
New height of an uploaded image will be defined according to the 
size ratio. For instance, if the image is 400x600 in widthxheight 
ratio and if you set width as "200" here, then the new size of the image
will be 200x300.
</documentation>

#---------------------------------------------------------
<description variable="image_annotate" topic="upload">
Annotate uploaded images? (ImageMagick required)
</description>

<documentation variable="image_annotate">
 To enable this feature simply select yes. It will insert a text on 
 the uploaded images.
 This feature had to be disabled by default because most of the
 the web hosts do not have imagemagick installed by default.
 You need to have imagemagick in your server to annotate images.
</documentation>

#---------------------------------------------------------
<description variable="image_annotate_text" topic="upload">
Text on annotated images?
</description>

<documentation variable="image_annotate_text">
This will be the text inserted into the image after upload.
You can use %login% variable inside this text.
</documentation>

#---------------------------------------------------------
<description variable="image_composite" topic="upload">
Composite a logo to uploaded images? (ImageMagick required)
</description>

<documentation variable="image_composite">
 To enable this feature simply select yes. It will insert a logo 
 image on the uploaded images.
 This feature had to be disabled by default because most of the
 the web hosts do not have imagemagick installed by default.
 You need to have imagemagick in your server to annotate images.
</documentation>

#---------------------------------------------------------
<description variable="image_composite_logo" topic="upload">
Logo on composited images?
</description>

<documentation variable="image_composite_logo">
This will be the logo inserted into the image after upload.
You should have this file under your image directory.
Example: logo.gif
</documentation>

#---------------------------------------------------------
<description variable="static_pages" topic="static profile">
Enable static profiles?
</description>

<documentation variable="static_pages">
Would you like to have static web pages created?
</documentation>

#---------------------------------------------------------
<description variable="static_url" topic="static profile">
URL for static profiles
</description>

<documentation variable="static_url">
URL address of the static profiles? Please 
type a URL that starts with <i>http://</i> .
<p>
With the '/' at the end.
</documentation>

#---------------------------------------------------------
<description variable="static_dir" topic="static profile">
Directory path for static profiles
</description>

<documentation variable="static_dir">
In which directory the url going to be? Please  type a path 
like "profiles"" (if in the same directory) or 
"/home/mydomain/public_html/profiles/"
<p>
With the '/' at the end.
</documentation>

#---------------------------------------------------------
<description variable="use_static_directory" topic="static profile">
Create directories for static profiles?
</description>

<documentation variable="use_static_directory">
 Create directory for static profile?
<p>
 "yes" means profile URLs like www.yourdomain.com/members/login
<br>
 "no" means profile URLs like www.yourdomain.com/members/login.html
</documentation>

#---------------------------------------------------------
<description variable="static_dir_additional" topic="static profile">
Additional directories for static profiles
</description>

<documentation variable="static_dir_additional">
If you would like to make multiple copies of the static profiles 
types the paths like this:
"profiles1", "profiles2", "profiles".a
<p>
You probably don't want this. Some users have multiple domain names, and would 
like to create copy of the static URL on different domains. This is useful if you 
would like to do that. 
</documentation>

#---------------------------------------------------------
<description variable="static_extension" topic="static profile">
Extension for static page
</description>

<documentation variable="static_extension">
Page extension for the created static profile pages. 
For instance if you will have server side includes in the 
page, you can define it as "shtml". Or if you will have a 
PHP code, you may define it as "php". 
</documentation>

#---------------------------------------------------------
<description variable="content_htaccess_file" topic="protected directory">
Member Only htaccess file location
</description>

<documentation variable="content_htaccess_file">
To protect a directory apache uses htaccess files.
- IPs of the users into this file.
- The password file will be pointed from this file.
<br>
</documentation>

#---------------------------------------------------------
<description variable="content_pass_file" topic="protected directory">
Member Only htpassword file location
</description>

<documentation variable="content_pass_file">
To protect a directory apache uses htpassword files, 
the script will create and write to this file.
<br>
Then the .htaccess file will point to this password file to 
enable access for (approved or all) users.
</documentation>

#---------------------------------------------------------
<description variable="content_pass_www" topic="protected directory">
Member Only URL of protected directory without "http://"
</description>

<documentation variable="content_pass_www">
The script will link to the password protected directory like this:
<br>
http://LOGIN:hide@address.com/members-only
<p>
Type www.yourdomain.com/members-only part for this purpose.
</documentation>

#---------------------------------------------------------
<description variable="htaccess_use_id" topic="protected directory">
Use an ID for the protected area(not real password)
</description>

<documentation variable="htaccess_use_id">
Each user has a unique ID in the database, if you choose to do so, these IDs can 
be used instead of password for the password fields of the protected area. 
<p>
This is useful if you would like to link to the member's only area like the URL below and if you don't want 
the password to be avaliable to be seen on the location bar.
<br>
http://login:hide@address.com/member-only/
<p>
Using this feature, you can link to the protected area like this:
<br>
http://%%login%%:%%password%%@www.youdomain.com/member-only/
<p>
Note that, since IE started to block this feature, we now recommend using 
approved action.
</documentation>

#---------------------------------------------------------
<description variable="htaccess_autoapprove" topic="protected directory">
Approve users on registration?
</description>

<documentation variable="htaccess_autoapprove">
 Should the users be approved when they register
 or will you approve them manually from the admin panel?
<p>
 yes: auto-approve users when they register
<br>
 no: no access to members-only protected directory and approved actions 
until I approve them from admin panel
</documentation>

#---------------------------------------------------------
<description variable="can_unapproved_login" topic="protected directory">
Can not-yet-approved user login?
</description>

<documentation variable="can_unapproved_login">
 Can not-yet-approved and disapproved members still login?
<p>
 The default mode for approval only restricts the access to
 the content directory. Though you can use it to restrict
 logins.
</documentation>

#---------------------------------------------------------
<description variable="max_htaccess_ips" topic="protected directory">
Maximum Allowed IPs
</description>

<documentation variable="max_htaccess_ips">
When a member enters into the member's only directory, his/her 
IP address is added to the allowed IPs list in the .htaccess file.
This is a first-in-first-out list. If you keep this number too low, 
people will not have access for the protected directory for very long. 
If you keep it too high, then they will have access for long time.
</documentation>


#---------------------------------------------------------
<description variable="use_header" topic="templates">
Enable header?
</description>

<documentation variable="use_header">
Enable header on all pages. Header is the 
"templates/header.htm" file, and if enabled, it will 
show up on top of all pages.
</documentation>
#---------------------------------------------------------
<description variable="use_footer" topic="templates">
Enable footer?
</description>

<documentation variable="use_footer">
Enable footer on all pages. Footer is the 
"templates/footer.htm" file, and if enabled, it will 
show up on bottom of all pages.
</documentation>

#---------------------------------------------------------
<description variable="tempz" topic="templates">
Template List
</description>

<documentation variable="tempz">
This is the list of all templates on the system. 
They are located at "templates" directory. 
They can be modified using FTP or through admin panel.
</documentation>

#---------------------------------------------------------
<description variable="init_errors" topic="templates">
Error Messages
</description>

<documentation variable="init_error">
This is  the list of most of the error messages. 
You can customize them to your language or to a better grammer. :)
</documentation>

#---------------------------------------------------------
<description variable="show_tempz" topic="templates">
Additional Show Templates
</description>

<documentation variable="show_tempz">
This is useful to add pages to your members area.
Listing of all template who supports "show" action. 
<p>
Show action should be used for pages that are not protected, while you still would like to use %%tags%% in the pages. Show action does not perform a password or ID check on the page. The tags you can use are the ones that are general tags like %%no of members%% or the information you send using a form or URL. Since show does not check login and password/ID information, it will not provide any information about the user from database for security reason.
</documentation>

#---------------------------------------------------------
<description variable="member_tempz" topic="templates">
Additional Member Templates
</description>

<documentation variable="member_tempz">
This is useful to add pages to your members area.
Listing of all template who supports "member" action.
<p>
Member action should be used for pages that are protected. It performs a password or ID check on the page. The links to these pages should include the users %%ID%%. You can retrieve and use any information about the user in these pages. The user will get a permission error if the ID/password is not correct.
</documentation>

#---------------------------------------------------------
<description variable="approved_tempz" topic="templates">
Additional Approved Templates
</description>

<documentation variable="approved_tempz">
This is useful to add pages to your members area.
Listing of all template who supports "approved" action.
<p>
Approved action should be used for pages that are only avaliable to approved members from admin panel. It performs a password/ID check, and it checks if the user is approved . The links to these pages should include the users %%ID%%. You can retrieve and use any information about the user in these pages. The user will get a permission error if the ID/password is not correct, or if he/she is not approved.
</documentation>

#---------------------------------------------------------
<description variable="monthz" topic="templates">
Months
</description>

<documentation variable="monthz">
 Change if you would like to use  
 names in different languages
 or numbers instead of words.
</documentation>

#---------------------------------------------------------
<description variable="date_format" topic="templates">
Date Format
</description>

<documentation variable="date_format">
How should be the date showed ?
<br>
%date%: will be relpaced by day
<br>
%month%: will be replaced by month
<br>
%year%: will be replaced by year
</documentation>

#---------------------------------------------------------
<description variable="list_max_list" topic="listing">
Listing results per pages
</description>

<documentation variable="list_max_list">
 Maximum number of profiles in the listing results.
</documentation>

#---------------------------------------------------------
<description variable="list_next_link" topic="listing">
Next link text for listing and search 
</description>

<documentation variable="list_next_link">
On listing and search result pages this link will be used to 
link to the next page.
</documentation>

#---------------------------------------------------------
<description variable="list_prev_link" topic="listing">
Previous link text for listing 
</description>

<documentation variable="list_prev_link">
On listing result pages this link will be used to 
link back to previous page.
<br>
The search page started using a better approach. It uses 
a simple javascript back link. So this is only for list action.
</documentation>

#---------------------------------------------------------
<description variable="list_between_next_prev" topic="listing">
Text between next and previous links
</description>

<documentation variable="list_between_next_prev">
Text between next and previous links on listing pages.
</documentation>

#---------------------------------------------------------
<description variable="list_alphabetic" topic="listing">
Alphabetic listing?
</description>

<documentation variable="list_alphabetic">
In default mode, should it sort the listing results in aplhabetic order?
<p>
 yes:          will list the results in alphabetic order
<br>
 no:           will only show them in the same order as database
                       (registration or update order)
<br>
 random:       will show them in a different order everytime
</documentation>

#---------------------------------------------------------
<description variable="journal_list_max" topic="listing">
Journal listing maximum entries per page
</description>

<documentation variable="journal_list_max">
In journal listing page,  maximum entries per page.
</documentation>

#---------------------------------------------------------
<description variable="journal_search_max" topic="listing">
Journal search maximum entries per page
</description>

<documentation variable="journal_search_max">
Journal search results  maximum entries per page.
</documentation>

#---------------------------------------------------------
<description variable="disabled_save_last_logged" topic="user tracking">
Save last_logged time in database?
</description>

<documentation variable="disabled_save_last_logged">
If you choose "yes", you must also add a "last_logged" database field.
It will then start saving the time the user logged on last time.
</documentation>

#---------------------------------------------------------
<description variable="save_stats" topic="user tracking">
Save user browser and IP stats?
</description>

<documentation variable="save_stats">
Should the script save information about the user's browser, 
operating system and IP. These data is accessible through admin 
panel.
</documentation>

#---------------------------------------------------------
<description variable="track_user" topic="user tracking">
Track all user movements?
</description>

<documentation variable="track_user">
This option will log all user behaviour in a log file.
These data is accessible through admin panel.
</documentation>

#---------------------------------------------------------
<description variable="save_history" topic="user tracking">
Save history?
</description>

<documentation variable="save_history">
This option will log all user changes in a log file.
Currently there is no place on the admin panel to see these logs,
but you can download and look at the log with a text editor.
</documentation>

#---------------------------------------------------------
<description variable="save_search_history" topic="user tracking">
Log searches?
</description>

<documentation variable="save_search_history">
This option will log all searches in a log file.
These data is accessible though admin panel.
</documentation>

#---------------------------------------------------------
<description variable="online_users" topic="user tracking">
Enable "online users" feature?
</description>

<documentation variable="online_user">
To list online users, you need to enable this feature.
<p>
However, if you are not using this feature, disabling it is highly recommended. 
The reason? Simple, to speed up the script, since it won't deal with tracking 
user status everytime someone sees a page in the script.
</documentation>

#---------------------------------------------------------
<description variable="idle_minutes" topic="user tracking">
Idle time (in minutes) 
</description>

<documentation variable="idle_minutes">
Idle time in minutes to assume someone is offline.
This is useful if you have enabled the "online users" feature.
</documentation>

#---------------------------------------------------------
<description variable="database" topic="files and directories">
Location of main database file
</description>

<documentation variable="database">
The location for your pm.dat database file.
</documentation>



#---------------------------------------------------------
<description variable="stat_file" topic="files and directories">
Location of users statistics log
</description>

<documentation variable="stat_file">
The location for your stat.dat user statistics file.
</documentation>



#---------------------------------------------------------
<description variable="track_file" topic="files and directories">
Location of deleted accounts log
</description>

<documentation variable="track_file">
This is the track.dat file that logs the user behaviour.
</documentation>



#---------------------------------------------------------
<description variable="h_delete" topic="files and directories">
Location of deleted accounts log
</description>

<documentation variable="h_delete">
This is the deleted.dat file that logs the deleted accounts.
</documentation>


#---------------------------------------------------------
<description variable="h_modify" topic="files and directories">
Location of account modifications log
</description>

<documentation variable="h_modify">
This file logs the user data changes.
</documentation>



#---------------------------------------------------------
<description variable="h_search" topic="files and directories">
Location of search log
</description>

<documentation variable="h_search">
This file logs the user searches.
</documentation>



#---------------------------------------------------------
<description variable="online_file" topic="files and directories">
Location of online log
</description>

<documentation variable="online_file">
This file logs the online users.
</documentation>


#---------------------------------------------------------
<description variable="admin_pass_file" topic="files and directories">
Location of admin password file
</description>

<documentation variable="admin_pass_file">
This file saves the encrypted admin password.
</documentation>


#---------------------------------------------------------
<description variable="backup_folder" topic="files and directories">
Folder for backups
</description>

<documentation variable="backup_folder">
The database backups will be saved under this directory.
You can backup database from admin panel.
</documentation>


#---------------------------------------------------------
<description variable="count_db" topic="files and directories">
File for profile counter
</description>

<documentation variable="count_db">
This file saves the user counters on their profile.
</documentation>


#---------------------------------------------------------
<description variable="reserved_logins" topic="files and directories">
Reserved logins file
</description>

<documentation variable="reserved_logins">
You can block some login names by putting them to this file.
</documentation>

#---------------------------------------------------------
<description variable="basemessage" topic="messaging">
Message data fields
</description>

<documentation variable="basemessage">
This list contains the elements of internal messsages. 
If you would like to add a new field to the internal messages, 
simply add it to the end of the list, and include it in the mail 
writing and reading forms.
</documentation>

#---------------------------------------------------------
<description variable="mail_next_link" topic="messaging">
Inbox next link
</description>

<documentation variable="mail_next_link">
You can change this to translate it to your language.
</documentation>

#---------------------------------------------------------
<description variable="mail_prev_link" topic="messaging">
Inbox previous link
</description>

<documentation variable="mail_prev_link">
You can change this to translate it to your language.
</documentation>

#---------------------------------------------------------
<description variable="mail_between_next_prev" topic="messaging">
Inbox text between next and previous
</description>

<documentation variable="mail_between_next_prev">
On the message listing pages, this will be the text between next and 
previos pages links.
</documentation>

#---------------------------------------------------------
<description variable="mail_max_list" topic="messaging">
Inbox maximum listing per page
</description>

<documentation variable="mail_max_list">
The number of messages per page in the mail listing.
</documentation>

#---------------------------------------------------------
<description variable="mail_tables" topic="messaging">
Mail listing table start
</description>

<documentation variable="mail_tables">
 The header 
 of the mail result table:
</documentation>

#---------------------------------------------------------
<description variable="mail_tablee" topic="messaging">
Mail listing table end
</description>

<documentation variable="mail_tablee">
 The footer of the mail result table
</documentation>

#---------------------------------------------------------
<description variable="mail_last_message_first" topic="messaging">
List mails in latest message first order?
</description>

<documentation variable="mail_last_message_first">
In the mail listing page, show the latest message first(yes), 
or olderst message first?
</documentation>

#---------------------------------------------------------
<description variable="send_mail_notify" topic="messaging">
Email notify about new messages?
</description>

<documentation variable="send_mail_notify">
When there is a new internal message, send the user an email about it.
The body can be changed from "message_email" template.
</documentation>

#---------------------------------------------------------
<description variable="message_to_mail_subject" topic="messaging">
Subject for email sent to notify an internal message
</description>

<documentation variable="message_to_mail_subject">
 Subject field if this is a "mail and message"
 kind of message from admin panel. OR to notify the user if 
 there is a message in their inbox.
<br>
 Sends internal message and sends an
 email saying "you've got mail in your mailbox",
 they will have to go to the panel to read it
 the body part is in message_email template.
</documentation>

#---------------------------------------------------------
<description variable="use_quote" topic="random quote">
Enable random quotes?
</description>

<documentation variable="use_quote">
This will enable random quotes, so that you can show a random quotes 
from users in a page in your site. Like this
<p>
                Today's quote: "%%random quote%%" by
                &lt;a href=pm.cgi?action=display&login=%%quote login%%&gt;%%quote login%%&lt;/a&gt;.  
</documentation>

#---------------------------------------------------------
<description variable="quote_field" topic="random quote">
Database field showed
</description>

<documentation variable="quote_field">
You can use random quotes to show some other user database field. 
It doesn't have to be the quote entered by the user. You can put 
any database field here.
</documentation>

#---------------------------------------------------------
<description variable="todays_quote" topic="random quote">
Change quote daily (instead of random)
</description>

<documentation variable="todays_quote">
  What kind of random quote do you want;
<br>
  Daily random quote?
<br>
  yes: will show a quote for a day
<br>
  no: will show a different random quote
  every time it is being called.
</documentation>

#---------------------------------------------------------
<description variable="unix" topic="advanced">
Is this a unix type server?
</description>

<documentation variable="unix">
If your server is linux, unix, bsd, solaris etc., select yes.
Otherwise if this is a windows server, select no.
</documentation>

#---------------------------------------------------------
<description variable="timezone" topic="advanced">
Correct server time:
</description>

<documentation variable="unix">
If your server time is different than the time you would like to
use, simply use a number in this field. The number you use will
change the hour of the time. You can use negative numbers as well.
</documentation>

#---------------------------------------------------------
<description variable="admin" topic="advanced">
Admin login name
</description>

<documentation variable="admin">
what is the login name for admin account?
</documentation>

#---------------------------------------------------------
<description variable="strip_html" topic="advanced">
Strip HTML tags from user entries?
</description>

<documentation variable="strip_html">
 Strip html tags from any user input?
 This option is recommended as a security precaution.
Someone might put a javascript on their profile to do nasty stuff.
</documentation>

#---------------------------------------------------------
<description variable="use_cookie" topic="advanced">
Enable cookies?
</description>

<documentation variable="use_cookie">
If you would like to disable cookie use by the script, select no.
</documentation>

#---------------------------------------------------------
<description variable="flocking" topic="advanced">
File locking? (unix only)
</description>

<documentation variable="flocking">
Enable file locking? This will only work if you are
using a unix based system.
</documentation>

#---------------------------------------------------------
<description variable="encrypt_addon" topic="advanced">
Two letters for encryption
</description>

<documentation variable="encrypt_addon">
 To make the password encription
 more secure, write any two letters.
</documentation>

#---------------------------------------------------------
<description variable="can_repeat_email" topic="advanced">
Can create multiple accounts with same email?
</description>

<documentation variable="can_repeat_email">
If this is disabled, it is not possible to create a second account 
using the same email address used before.
</documentation>

#---------------------------------------------------------
<description variable="can_repeat_IP" topic="advanced">
Can create multiple accounts with same IP Address?
</description>

<documentation variable="can_repeat_IP">
If this is disabled, it is not possible to create a second account 
from the same IP address.
</documentation>

#---------------------------------------------------------
<description variable="assign_incremental_login" topic="advanced">
Assign Incremental Numbers as Login Names
</description>

<documentation variable="assign_incremental_login">
If set to "yes", this will look at the database and find the user login name 
with the highest number and add one to it. You should remove the login field
from the registration form, since it will be ignored.
<p>
If you would like it to start counting from a predefined number. Use the import tool 
to add an seed account with a login name as the number. Once another account is created 
afterwards, you can delete this seed account.
</documentation>

#---------------------------------------------------------
<description variable="blog_list_max" topic="listing">
Blog listing entries per page
</description>

<documentation variable="blog_list_max">
In blog listing page,  maximum entries per page.
It should be an integer.
</documentation>

#---------------------------------------------------------
<description variable="blog_search_max" topic="listing">
Blog search entries per page
</description>

<documentation variable="blog_search_max">
In blog search results page,  maximum entries per page.
It should be an integer.
</documentation>

#---------------------------------------------------------
<description variable="subscription_type" topic="subscriptions">
Subscription Type
</description>

<documentation variable="subscription_type">
Subscription type.  Do not edit this manually.
Instead, use admin -> payment -> setup page.
</documentation>

#---------------------------------------------------------
<description variable="payment_type" topic="subscriptions">
Payment Type
</description>

<documentation variable="payment_type">
Information about the payment. Do not edit this manually. 
Instead, use admin -> payment -> setup page.
</documentation>

#---------------------------------------------------------
<description variable="subscription_dir" topic="subscriptions">
Subscription Directories
</description>

<documentation variable="subscription_dir">
Protected Directories which are only available to particular type of subscribers!
</documentation>

#---------------------------------------------------------
<description variable="plugin_phpbb" topic="plugin_phpbb">
Integrate phpBB
</description>

<documentation variable="plugin_phpbb">
This will integrate registration, login, lougout and change password activities 
of PM to phpBB. To enable it, you need to first have a working phpBB installation in your site. 
Copy utils/phpbb/pm2phpbb.php file into you phpBB directory.
But you should first open this file and change its admin_access_key.
Then enter the URL of this file and the admin_access_key into configuration. 
You should be all-set.
</documentation>

#---------------------------------------------------------
<description variable="plugin_phpbb_url" topic="plugin_phpbb">
phpBB URL
</description>

<documentation variable="plugin_phpbb_url">
The location of your phpBB installation directory. 
Such as http://www.mydomain.com/phpbb
</documentation>

#---------------------------------------------------------
<description variable="plugin_phpbb_adminkey" topic="plugin_phpbb">
phpBB Access Key
</description>

<documentation variable="plugin_phpbb_adminkey">
This is a password PM uses to access phpBB database. What you set here 
must be exactly same as what you set in pm2phpbb.php file.
</documentation>

#---------------------------------------------------------
<description variable="app" topic="app">
Application List
</description>

<documentation variable="app">
</documentation>

#---------------------------------------------------------
<description variable="app_base" topic="app">
Application Fields
</description>

<documentation variable="app_base">
</documentation>

#---------------------------------------------------------
<description variable="app_base_descriptions" topic="app">
Application Field Descriptions
</description>

<documentation variable="app_base_descriptions">
</documentation>

#---------------------------------------------------------
<description variable="app_max_list" topic="app">
Application Listings Per Page
</description>

<documentation variable="app_max_list">
</documentation>

#---------------------------------------------------------
<description variable="searchform" topic="searchwiz">
Search Forms
</description>

<documentation variable="searchform">
</documentation>

#---------------------------------------------------------
<description variable="searchform_questions" topic="searchwiz">
Search Form Questions
</description>

<documentation variable="searchform_questions">
</documentation>

#---------------------------------------------------------
<description variable="searchform_listing" topic="searchwiz">
Search Form Listing Pages
</description>

<documentation variable="searchform_listing">
</documentation>

#---------------------------------------------------------
<description variable="category_url" topic="categories">
URL for static category pages
</description>
 
<documentation variable="category_url">
URL address of the static category pages? Please 
type a URL that starts with <i>http://</i> .
<p>
With the '/' at the end.
</documentation> 
 
#---------------------------------------------------------
<description variable="category_dir" topic="categories">
Directory path for static category files
</description>
 
<documentation variable="category_dir">
In which directory the files going to be created?  Such as
"/home/mydomain/public_html/directory/"
<p>
With the '/' at the end.
</documentation>

#---------------------------------------------------------
<description variable="category_field" topic="categories">
Category Field
</description>

<documentation variable="category_field">
Should be a dropdown field in the database.
</documentation>

#---------------------------------------------------------
<description variable="category_suggest_field" topic="categories">
Category Suggest Field
</description>

<documentation variable="category_suggest_field">
Should be a text field in the database.
</documentation>

#---------------------------------------------------------
<description variable="smilies" topic="database">
Smilies
</description>

<documentation variable="smilies">
To have a new smilie, add it to this list, then upload image into 
your images directory smilie_NAME.gif format.
</documentation>

#---------------------------------------------------------
<description variable="ratingroot" topic="rating">
Rating and Review Folder
</description>

<documentation variable="ratingroot">
This is the directory where the rating and review files for users will be saved.
This directory should not be accessible by browse, so it should be 
under data directory.
</documentation>

#---------------------------------------------------------
<description variable="review_per_page" topic="rating">
Number of Reviews Per Page
</description>

<documentation variable="review_per_page">
If number of review posts  are more than this number, they will be shown on 
the next page.
</documentation>

#---------------------------------------------------------
<description variable="rating_email" topic="rating">
Send Rated/Reviewed Emails?
</description>

<documentation variable="rating_email">
If you would like users to recieve an email after getting rated or revied, set this to yes.
</documentation>

#---------------------------------------------------------
<description variable="rating_email_subject" topic="rating">
Subject for Rated Emails
</description>

<documentation variable="rating_email_subject">
The subject line for the emails your users will receive when they get rated.
The body of the email can be modified from rated_email template.
</documentation>

#---------------------------------------------------------
<description variable="review_email_subject" topic="rating">
Subject for Reviewed Emails
</description>

<documentation variable="review_email_subject">
The subject line for the emails your users will receive when they get reviewed.
The body of the email can be modified from review_email template.
</documentation>

#---------------------------------------------------------
<description variable="" topic="">
</description>

<documentation variable="">
</documentation>



Return current item: Article Manager