| General
Build Settings: |
| Default template set to use. This affects
which template set is used when building HTML pages, or when calling the cgi scripts without arguments. |
| build_default_tpl |
<%if cfg_build_default_tpl%>
<%Links::Tools::template_dir_select ($cfg_build_default_tpl, 'build_default_tpl', 'no_php')%>
<%else%>
<%Links::Tools::template_dir_select ('', 'build_default_tpl', 'no_php')%>
<%endif%>
|
| Number
of days old for a link to be considered new. |
| build_new_cutoff |
|
| This
determines what links are placed in the What's Cool area. If
> 1, the top n links will be considered popular. If < 1, the top
n% links will be considered popular. |
| build_pop_cutoff |
|
| Have
Links SQL automatically create a backup of the data every time you build
pages? |
| build_use_backup |
CHECKED<%endif%>>Yes
CHECKED<%endif%>>No |
| Generate
a category list. If you have a long set of categories, set this to No so
that you don't get very large drop down lists. |
| db_gen_category_list |
CHECKED<%endif%>>Yes
CHECKED<%endif%>>No |
| A
list of fields that will be set when a user adds a record. It will
override anything the user puts in. |
| add_system_fields |
|
| Validation policy. The default
and recommend setting is that all links must be validated before being entered into the directory.
However, you can change this so user contributed links are auto-validated, or links contributed by authenticated
users are auto-validated. Note: no validation email will be sent to the user for auto-validated links. |
| build_auto_validate |
CHECKED<%endif%>> Admin/Editors approves all links (recommended)
CHECKED<%endif%>> Links submitted by authenticated users are auto validated.
CHECKED<%endif%>> All links are automatically validated (not recommended). |
| Only
allow additions from the following sites: |
| db_referers |
|
| Page
Display and Sorting Options: |
| The default sort orders
to use for sorting links on the Category, New and Cool pages. |
| build_sort_order_category |
|
| build_sort_order_new |
|
| build_sort_order_cool |
|
| build_sort_order_editor |
|
| Span
pages: set to yes and Links SQL will generate a separate html
pages for each n set of links in a category. It will also split
apart the what's new listings into separate html pages based on
date. |
| build_span_pages |
CHECKED<%endif%>>Yes
CHECKED<%endif%>>No |
build_links_per_page |
|
| Determines
whether to group links by the category they are in for the New and
Cool pages. |
| build_new_gb |
checked<%endif%>>Yes
checked<%endif%>>No
|
| build_cool_gb |
checked<%endif%>>Yes
checked<%endif%>>No
|
| Column to use to sort the
category listings. |
| build_category_sort |
|
| Use Yahoo style related categories (this will
put the related categories grouped in with the main categories, prefixed with an @ sign. If you use this, you can only
sort alphabetically. |
| build_category_yahoo |
checked<%endif%>>Yes
checked<%endif%>>No
|
| Number
of columns your subcategory list will be divided into. |
| build_category_columns |
|
| HTML to use
in table tag for subcategory listings. |
| build_category_table |
|
| Enable/Disable
the ability to display pages dynamically using the page.cgi script. If
set to yes, you can specify a comma separated list of values that will
be preserved as the user moves from page to page. Not usually necessary
to change. |
| dynamic_pages |
CHECKED<%endif%>>Yes
CHECKED<%endif%>>No |
| dynamic_preserve |
|
| Compress
all output, this will reduce file sizes of generated html by 10-20%. |
| compress |
CHECKED<%endif%>>Yes
CHECKED<%endif%>>No |
| File
and Directory Options: |
| Set to yes and Links SQL will build a
separate HTML page for every link. Note: you must create the link to the detailed page yourself. This can be
done by placing a link to the detailed page in the link.html template using <a href="<%detailed_url%>">. |
| build_detailed |
CHECKED<%endif%>>Yes
checked<%endif%>>No |
| Index
page to use for new directories; page that is pulled when you request a
directory. |
| build_index |
|
| Extension
to use on non index pages. |
| build_extension |
|
| Use foreign characters? This will change how Links SQL builds it's
category pages, it will use the ID number instead of the Category Name as
a directory. If you are using GB or Big5 encoding, you should make sure to use
the regular search and not the indexed search. This can be set in the Search Options. |
| foreign_char |
CHECKED<%endif%>>Yes
CHECKED<%endif%>>No |
| Instead of creating directories based on category names, you can add a
separate field to the Category table, and use that field to store the directory
name. Some warnings: Make sure the field is unique to avoid collisions, and make sure you put a good reg exp to validate the input. Leave blank unless you know otherwise. |
| build_directory_field |
|
| Directory
permissions to use, default to 777 so that you can remove the
directories from FTP/telnet as usually they are owned by the web
server. |
| build_dir_per |
|
| File
permissions to set newly created pages to, use 666 if you want to switch
between building from telnet, and building from shell. Use 644 if you
are going to be running under cgiwrap, or only building from telnet. |
| build_file_per |
|