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. If you have different themes set up, then
they will show up as "<template set>.<theme>".
|
build_default_tpl |
<%Links::Tools::tpl_dir_select($cfg_build_default_tpl, '(?:browser|admin)', '', 1)%>
|
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 Gossamer Links automatically create a backup of the data every time you
build pages?
|
build_use_backup |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
Whether or not Gossamer Links should generate a category list when a
category needs to be selected. If 'No' is selected, the user will have
to view the category they wish to add the link to before clicking on
'Add a Link'. If you choose to display the category list, then you have
two choices: an AJAX category selector (recommended if you have a lot of
categories), or a simple select list dropdown. Note that users must have
javascript enabled and have a browser that supports XMLHttpRequest before
they can use the AJAX category browser. If you choose to use the AJAX
category selector, then it will also be used on the admin side. For it
to function correctly, your default template set must have the
treecats.xml file.
|
db_gen_category_list |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
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 |
|
A comma separated list of template variables that are protected. These
variables will not accept input from CGI (ie. arguments passed in through
the web) and will default to an empty string if they aren't directly
passed in as variables to the templates.
|
protected_vars |
|
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 anonymous users are auto-validated. Note: no
validation email will be sent to the user for auto-validated links.
|
build_auto_validate |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
Only allow additions from the following sites:
|
db_referers |
|
A comma separated list of Links columns which, if updated, will update the
Timestmp of the categories the link is in. You should only need to add a
column to this list if you use the column in link.html, the column data
changes often, and are using "Build Changed". For example, if you use
<%Hits%> in link.html and don't add it to this list, then the
category page won't be built on "Build Changed" when the Hits is updated.
|
links_cols_update_category |
|
Page Display and Sorting Options: |
The default sort order to use for sorting links on the Category page.
|
build_sort_order_category |
|
<%if config.payment.enabled%>
Whether or not to show paid links first, above free links, on the Category page.
|
build_sort_paid_first |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
<%endif%>
The default sort order to use for sorting links on the new page.
|
build_sort_order_new |
|
The default sort order to use for sorting links on the cool page.
|
build_sort_order_cool |
|
The default sort order to use for sorting links on the editor page.
|
build_sort_order_editor |
|
Page spanning: if enabled, Gossamer Links will break up large numbers of links
in a category onto multiple pages.
|
build_span_pages |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
build_links_per_page |
|
Whether or not to split apart the what's new listings into separate pages based on date.
|
build_new_date_span_pages |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
These options determines whether or not links will be grouped by category
on the New and Cool pages.
|
build_new_gb |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
build_cool_gb |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
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="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
Number of columns your subcategory list will be divided into. Note that this option is deprecated - you should only need this if you are using version 2.x templates.
|
build_category_columns |
|
HTML to use in table tag for subcategory listings. Note that this option is deprecated - you should only need this if you are using version 2.x templates.
|
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="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
dynamic_preserve |
|
A comma separated list of pages in which you wish to preserve sb, so,
cat_sb, cat_so and Links column (for filtering) values. These
sort/filtering options only work on category and detailed pages, but if
you have custom category/detailed pages, then you will want to add them
to the list. Regular expressions can be used.
|
dynamic_preserve_sort_pages |
|
Generate 404 Status codes for requests to page.cgi that do not match a valid
category. This can be useful when you use rewrite rules to send all requests
to page.cgi.
|
dynamic_404_status |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
Any URLs in the templates that begin with the build_root_url will get
transformed into a dynamic URL for use with page.cgi. If you have URLs
that should not be transformed, then add them to this list. You may use
config tags such as <%build_root_url%> and
<build_static_url%>. Enter one URL per line.
|
dynamic_no_url_transform |
|
If enabled, extra whitespace in generated HTML will be
removed, reducing the size of generated HTML pages by
up to 20%.
|
compress |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
File and Directory Options: |
If enabled, Gossamer Links will build a separate HTML page
for each link.
|
build_detailed |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
Filename to use for the home page. If this is left blank, then the build_index option will be used for the filename.
|
build_home |
|
Index page to use for directories; page that is pulled when you request a
directory.
|
build_index |
|
Whether or not the build_index is appended to URLs. Turning off this
option allows you to switch between different index page types without
affecting bookmarked pages or search engine rank. Note that if you turn
this option off, then your webserver must be configured to use the
build_index as the index page.
|
build_index_include |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
Page name to use for pages that span more than one page. The full name will be [build_more][page #][build_extension].
|
build_more |
|
Extension to use on non index pages.
|
build_extension |
|
Whether or not the Full_Name format variable should behave like it did in
Links SQL (where it did no coalesce multiple _'s into a single _). If
this is a new installation, then keep this set to 'No'. If you have
upgraded from a previous version, and want to ensure all your urls are
kept the same, then set this to 'Yes (broken)'. The difference between
the 'Yes' and 'Yes (broken)' settings is that _'s are not coalesced for
the Full_Name variable in build_detail_format for the 'Yes' setting.
|
build_format_compat |
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
checked="checked" <%endif%>/>
|
This option controls how the directories for categories will be named.
Note that if your category names contain many or entirely foreign
characters, the ID-only option is recommended. The two "shortened" ... forms
substitute long portions (>20 characters) of the category name with
"...", removing either characters off the beginning or end of the name.
The shortened forms without ... simply remove extra characters without
substituting them. The advanced option can be used to specify a custom
format string, but is not recommended for casual users. See
Links::Tools::parse_format for more details.
|
build_category_format |
style="display: none"<%endif%> />
|
This option controls how dynamic URLs will look. The
"ID" setting will result in URLs such as
page.cgi?g=123;d=1 while the "Full_Name" setting will result
in URLs such as
page.cgi?g=Category/Name;d=1 . Gossamer Links will always accept
both URL forms, this setting simply controls the
default when Gossamer Links generates dynamic-mode URLs.
You may alternatively choose another field, but be aware that this
will cause problems if the column does not contain unique values
for every category.
|
build_category_dynamic |
style="display: none"<%endif%> />
|
This option controls how detailed pages will be named. The default is
simply the link ID, but more complex paths are possible. If the format
does not contain the link ID, the link ID will be appended to the end of
the format (_LinkID). The "shortened" option substitutes portions of the
category name longer than 15 characters, and portions of the link title
longer than 20 characters with "...". The advanced option can be used
to specify a custom format string, but is not recommended for casual
users. Note: This option only applies when the
build_detailed option above is enabled.
|
build_detail_format |
style="display: none"<%endif%> />
|
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 |
|