If you enable Demonstration Mode, you grant read only access to most addedValue plugin pages, even to non editors. Normally only Managing Editors can see these pages. Any form buttons that actually cause a change to are disabled. This option is intended to help with learning addedValues. The demoModeLink macro creates a link to the addedValues homepage if the preference is set.

If you enable Developers Debug Flag a lot of information - typically on a yellow background - is displayed on many pages. Some forms have extra buttons. A less intrusive variant Member Debug Flag is a member specific preference that shows only some of the debug information. This may be helpful for advanced scripters who want to study some of the techniques used in addedValues.

Setting Use popup windows for help text removes the help text from some, but not all, editing pages and adds a link that opens a popup window near the buttons of each form. The object is to make smaller pages that load faster.

Setting Show developers notes adds a link to the various addedValues selection boxes for variables, report, forms etc. which enable creating, and viewing notes from a web site developer to another about that entity.

Setting Class on AV forms/buttons adds a class - class='addedValues' - to every form used internally by addedValues. It also surrounds every input button in those forms with a span with a class of addedValuesButtons - <span class='addedValuesButtons'>.

Setting Publish Tropes turns on the trope server feature; which enables remote users to install self contained web applications (tropes) from your website into their website.

If you enable Track Recently Changed Pages, addedValues will track the most recently changed pages in the discussion group and add to the Edit this page form. By selecting within the multibox, you may limit the types of pages that are tracked; if you select nothing, changes to all messages are tracked. You can also determine the maximum number of pages tracked. Use the recentlyChangedPages macro to reports on the changes.

These preference determine the look and feel and response of the variables defintion form.

Language codes are used to index variables which are keyed by language. You can choose the languages needed for your purposes, from language codes defined in ISO 693 standard .

These options set various defaults of the rendering process and the settings on the forms entry page.

Default Date Formatter determines how dates are presented in reports if it doesn't otherwise specify formatting for a variable. It is also the format used by the siteLastModified macro if its dFormat parameter is empty.

If you enable Cache Results in Page, the page macro will keep a cache of pages it builds This trades memory overhead for an increase in speed of response for complex pages.

Setting Log all searches, causes addedValues to write an entry into the Frontier log for each search, containing the origin of the search, the form name, the combination of search items requested, the number of hits returned and the time in ticks to perform the search. The searches are logged under the sitename category.

The value of Pause index loop ops after, controls the speed of some index operations in a query (those marked "slow") by yielding the processor when a certain number of index entries have been processed. The higher the value, the less interruptions, but at the expense fo searches competing for CPU at the same time.

Text Indexing treats a string as a sequence of words which are indexed separately. The regular expression pattern determines what string of characters addedvalues treats as a word. This is not a preference to change lightly, because doing so invalidates all current text indexes and they must be manually rebuilt.

You can also create and maintain a list of stopwords, words which are never to be indexed. The current list for your site can be inspected here.

• Type
• test
• phrase
• here

Manila 9.5 or later (or in earlier versions another manila Plugin ManilaFixer,) can restrict access to messages to groups of members called Cohorts. See documentation for details. AddedValues can make use of Message Level Access Control in 2 ways

• to be more precise about which members can update certain variables.
• After a query or a search, remove inaccessible messages from the resulting hit list.

The Editable By menu controls who can edit a variable. It is found in the variables detail page you see when you select a vriable and click Edit. Enabling the preference to add cohorts to it, gives more precise control.

If MLAC is enabled and active in your site, and some messages are controlled and potentially inaccessible to cohort members, it's still possible that a hit list can link to them. This may be desirable; if not set the 'Trim hit lists using MLAC' preference to purge inaccessible messages.

Addedvalues keeps track of the usage of variables, reports, etc. in your website. It does this so that it can prevent you from deleting inuse objects. To do this completely it has to analyse every macro call as messages and templates are changed because most references to reports, forms and queries appear there . addedValues is intelligent about what fields it checks, but checking adds an unavoidable additional overhead to creating or modifying a message. Therefore this feature makes most sense in complicated sites, or where more than one person works on site. Not all references can be evaluated at message save time, for example if the report name parameter to the page macro is itself a macro call, the usage actually made at run time will not be tracked.

Setting Track usage in messages the first time is an intensive operation, it requires examining every variable in every message. It s normal for this to take some time. After that first pass, data gathering occurs when a message changes.

Manila can "static render" a site; which means to write pages which may served by a static webserver such as Apache or Microsoft IIs. Links within the dynamic website are altered to point to the corresponding pages in the static version. However static servers cannot handle submissions of forms or run addedValues queries, so request for pages with these features must be referred to Frontier/Manila/addedvalues.

Pages with queries might change infrequently enough to justify static rendering them after each change. Queries may have next and previous links on their result pages, but static servers can serve such page if the webserver has a sufficently powerful server side include feature. For example Apache version 1.2 and later has conditional SSI diretives; whereas IIs does not. Consquently, Apache servers are good for queries with next and previous links, but IIs is not.

Replace some of standard urls Manila works with, with tailored ones. They will be enabled at plugin enable time and will revert to standard Manila urls at plugin disable time. This feature allows you to redirect those functions to pages which use addedValues, but only when the plugin is enabled in your website. This is an advanced option and casual usage can make a website unusable, so care is advised.

Only comparatively safe urls can be changed here. To change one url, enter the new url in the corresponding texbox. Once changed a url can be restored to the standard value by checking the revert box on left of the changed url.