addedValues Plugin

...Powerful Free! Database Expansion for Manila

(1 or more words)

Get tropes here!
Click to see internals
Report bug

Knowledge Venue

Viewable with Any Browser

Join Now


placeholder page

b148 - 2 new report qualifiers have been implemented to handle reporting all values of a multiple valued variable in a report. UL and list. list presents a comma delimited list of values, UL uses a UL HTML tag and individual items in li tags.

b164 - a Search results report can now specify a text, which is displayed if the search/query returns no results. The text will be set to empty for existing reports when the plugin is next enabled on each website. Until the enable is done searches that yield no hits will fail .

b179 - the test button on the reports page now works for item detail reports. You are asked to supply an appropriate context (a message number or shortcut for message reports, a member key for member reports, etc.). The report is displayed for the context supplied.

b183 - a new reports qualifier was added that returns the number of items in a value; 1 for a single valued variable; the number of current values for a multiple valued variable and the number of items in a list valued variable (builtins alsoListedIn and responses)

b200 The labelLookup qualifier for variables reports is now implemented; [[variable labelLookup(global variable)]] means look for the value of variable in the value list of global variable and replacing the title with the value.

b227 - the reports master page now adds a one character prefix to each report name in the multibox which indicates the report usage. Also reports with variables from a group display the groupname in parentheses after the report name.

b230 - a new option, Add Delete Button, was added to picklist reports. If enabled it adds a delete button to the form created by a picklist report. The name of the button can also be changed. The user is allowed to delete only messages that he would be able to edit. The placement of the button is determined by the layout of the picklist report. Coupling such a report with a form or query is a powerful way to delete some but not all of a certain class of messages. Messages deleted in this way are eligible for an undelete operation (by Manila) .

b235 - Secure RSS feeds. A new report option, "RSS feed must be SSL" is available for Reports whose usage is RSS. If set, it ensures that any calls to the rssLink macro will generate urls with https:// schemes and that all RSS feeds using this report use a secure server. This requires that Frontier be running a SSL capable web server; such as the one supplied by Macrobyte Resources (<>). If a feed is requested from a none SSL url (http scheme rather than https) , addedValues attempts to redirect the request to the corresponding secure port, an attempt that may fail if a secure server isn't installed (fails with script error) or isn't running (browser detects timeout).

b236 - a new option was implemented to run a special script to provide summary values for grouped reports. When addedValues is processing a hit list and comes to the last hit with one value of sortedBy, if a script called groupEndScript is found in a report table, it is run and passed the site address, the address of the hit list and a table where it can add entries; which will be used to replace strings such as [[a]] by the value in table.["a"]. This is intended for advanced developers.

- two new pseudo macros are available in message hit reports. reportPageLink create links to special addedValues page that runs a designated report for the message corresponding to the hit and optionally sets the page template to designated value. emailthispage creates a link to the addedValues mail this page passing the designated report. Both macros also accept a optional value of target.

b237 - In reports, the template used to render the mail this page form , can now be specified as an optional third parameter of the mailthispage pseudomacro. Other cosmetic and minor bug fixes were made to the mailthispage feature.

b237- A form of conditional if statement has been quietly supported in reports for a long time; it has the syntax
{if boolean expression {string expression} else {string expression}}
Until now, the string expressions were not evaluated in the current context, so if they variable references they were not expanded, which meant they had to be static strings. Now this limitation has been removed, and a lazy run time evaluation is done. Lazy means that only the expressions whose values are needed, are evaluated; therefore that side effects are avoided, there is only a small speed penalty and the strings expressions can be. or include other if statements. For example, given the message variables textBoxwanted, TextBoxShortcut, a report could contain

{if textBoxwanted {if TextBoxShortcut != "" {manilaExtras.includeViaShortcut(TextBoxShortcut)} else {"box goes here"}} else {""}}

b250- a line was added to the option shown for a report with a groupend script. Groupend scripts are run at the point addedValues breaks a report on the sortedBy variable value. There is no user interface to associate these scripts with a report, they must be added manually by the server administrator.

b250 - it is now possible to call a query and pass its hits to a report inside another report. The value of this technique is that the query runs in the context of the current context being processed by the first report (message of a hitlist, for example). The syntax is
[[call query("queryname", "reportname")]]
[[call query("queryname", "reportname", sortedby variable name")]]
The parameters have the same meaning and semantics as they do in the query macro.

b251- reports will now execute a script at the end of preparing each page; if the server administrator installs a script called pageendScript in the report table. (advanced option only).

b255 - a new report option for Item Details reports allows disabling the automatics tag neutering of the report template. Once enabled, that report cannot be used in the page macro, but it can still be used in a serveReportLink macro call. This change allows reports to construct arbitrary text with non standard tags used by Microsoft media player and similar applications.

b261 - A new pseudomacros [[lintotrackbackurl][] is now permitted in message search reports. It is intended to support an addedValues implementation of news pages.

b261 - the default export report for messages is now in the format expected by the XMLtoDG import extension.

b263 - the xmlencode report qualifier is now permitted in all kinds of reports.

b264 - a hitherto hidden report qualifier - hitnumber - is now available to report writers.

b268 - addedValues can have many RSS feeds each which might require different values for some of the header fields, so an RSS report may now have a configuration form and a header report that is used to build the header. The name of the configuration form and the header report need to be in a user table in a group with its own variables; and are configured using the show options set options buttons on the form master page.

b268 - the parser for reports, and forms now accepts builtins Frontier.version() and addedValueMacros.version.

b269 - - the psueduomacro shortcuturl is now permitted in reports. It assumes the value is a Manila shortcut and returns the url from the img src or a href. Its mostly useful for RSS reports, but can be used anywhere.

b269 - In search reports and tabulation reports, a new pseudomacro - hitpagelinks - can be used in the page layout templates. If used it returns a space delimited set of links to the start of each page of hits, in the same manner as Manila displays a list of stories or pictures.

b269 - in reports, a new builtin function - forEachCount(rowname) is permitted between the foraAch and forEachEnd pseudo macro, it returns he literal number that counts the iterations to date thru the foreach loop. Its isn't valid outside a forEach forEachEnd braketed segemtn fo reprot text; and the rowVariable parameter must match that used in the forEach.

b275 - reports with nested conditional statements inside foreach loops have been optimised, so that only the minimal evaluation needed is done.

b275 - a warning is now issued if a report option Neuter tags is disabled, the report text is submitted for validation and then the neuter tags option is enabled again. In this case addedValues will not run the report until the report text is validated again. The warning simply informs the editor that this is the case.

b281 - search reports can be associated with queries (query macro) which may have parameters. Previously the parameters were not accessible in the report, now the pseudomacro [[parameter XX]] returns the run time value of the query parameter called XXX. Since the names of the parameter cannot be checked as the report is defined, a check is made that parameter names used in the report actually exist in the query; if not an error is issued and the query doesn't run.

b284 - Until now the search report pseudo variables hitsperpage, totalhits, firstpagehit, lastpagehit, hitspergroup in header layout text and hitnumber, hiturl, hitkeyvalue, and hitdgurl in report layouts were not permitted as the parameters of macros and builtin functions. Now they can be used freely inside macro evaluations , subject to normal addedValue type checking - without the [[ and ]] delimiters or being quoted, for example, {string.percent(firstpageHit, totalHits, 2)} or {"hit " + addedValueMacros.getlink(hitnumber, hiturl)}

b284 - if the configuration form for an RSS report i invoked, the feed cache is rebuilt on the next hit. Setting the debug preference or the debug member preference causes the feed report to be run for every hit.

b284 - Hitlist filtering is the ability to review the results of a query, the hitlist, manually and remove elements before calling up the report which displays the results. It is most useful if the report will be printed or exported in some way. To enable hitlist filtering, set the new search report option from the dropdown menu called "Choose a manual filter'. That menu will only exist if there are picklist reports for the same attribute of and groupname as the search report you are filtering and which have the new option 'Enable hitlist filtering?' set. When a query macro call uses a filtered search report, addedValues will first display the hitlist with the picklist report and permit discarding any of the hits, until the continue button is clicked. Then the reduced hit list will be displayed using the original search report.

b284 - the builtin report - m5_showindex - which addedValues uses to display message indexes was improved. The new report will only be used if you delete the current report of that name and disable then enable addedValues. You are free to change this report at any time. Another builtin report - m5_showindex_gems - was added that addedValues will use to show gems indexes.

b284 - the demo mode preference in addedValues now allows viewing, but not setting, options of forms, reports and queries. Viewing of forms, reports and query options/configuration special pages are also now generally visible in demo mode.

b285 - - the display of item details report using the page macro in access controlled sites can now be restricted to members of one cohort, by setting the accessibleTo option to a cohort name. All reports are always rendered for Managing editors. This feature probably make most sense when one report calls another (with the page macro) whose access has been restricted. Inaccessible reports render as the string <!--- controlled report reportID not accessible--> for debugging purpose.

b286 - the debug information for item detail reports has been expanded to show report conditionals and loops.

b286 - a macro equivalent of the report pseudo macro [[variable values]] has been implemented. {values(variables)} returns the number of values of variable name in the current entity. It works for row placeholder variables, returning the number of rows.

b286 - 2 pseudo macros have been created for use in update and row update forks only. goBackURL contains the referer attribute of the page upon which the form was first created. goBackButon contain a tag that look like <input type='button' name='done' value=' Back '> with a javascript onclick handler that goes back to that saved page url. The gobackURL is available for general use.

b288 - in reports the pseudo-macro [[call report("xxx")]] is equivalent to {"xxx")}, except that addedvalues notes the usage of report xxx in this report.

b290 - search reports now allow the accumulation of the hitkeyValue to a multiple valued Search Report variable of type string. This allows the technique of gathering the unique values of the sortedby variable into a single variable whose value can be used in group or page layouts.

b293 - the order in which rows are processed by a forEach loop can now be modified by specifying one of the column variables of the row placeholder as sort key. The revised syntax is [[rowvariable foreach("sortvariable")]]. sortvariable must be a column in the row place holder variable rowvariable. Sortvariable is optional, the old syntax still works as before . The order that rows are processed in is always native sort order ascending.

b294 - a new variant of the forEach looping construct in reports - forEachWhere, was implemented. Its effect is to loop thru all rows of a row placeholder table; but discarding those that do NOT satisfy a condition. The new syntax is [[rowvariable foreachWhere(boolean expression; optional sortby column variable)]] [rowvariable endForEach]] boolean expression contains the same range of possibilities as a virtual variable; it may reference all variables from he same context, except multi-valued column variables of the a different row placeholder or values from another row of the same row placeholder. However, it may also contain macros.

b296 - the forEach, forEachWhile, forEachCount and endForEach qualifiers in reports have been extended to work with non row placeholder multiple valued variables. The syntax is the same, except that you may not specify the order in which the rows are displayed. The display of multiple values of variables could already be formatted with list or UL qualifiers, but using a foreach loop extends the possibilities significantly, allowing macro calls and expressions within macro brackets, for example.

b304 - In a report ,qualifying a variable with reportpagePopup, returns a link to a popup window whose text is the variable value. You may specify the template , width , height , scroll and resizable properties of the window, as in the addedValueMacros.reportPageLinkPopup macro.

b305 - in hit reports for messages ; the reportpagePopup qualifier creates a popup window link to the hit message, the contents of the window are determined by a report , the layout optionally by a template , and the window properties of width, height, scroll capability and resize-abiliy are all parameters. When a page with an addedValueMacros. search macro call is statically rendered , any popup windows link generated with reportpagePopup will be served by the static server. addedValues generates pages for each popuwindows and contrives that the popup windows use static server urls

fc2 - picklist reports can now optionally have a Render (this page) button; which is added to the picklist page or group layout using [[picklistRender]]. If clicked , checked items on the picklist reports results page - which have one or more paths in the site structure - are rendered to the static site. When a message is rendered, pages are rebuilt for each relative path; hitList candidates that have no paths are skipped, as are paths for which the path Attribute noStaticRender is true. This feature is a programmable "render this Page" button , with the advantage that a query (or a search form) can be used to select candidates. The option is not available in a website unless static rendering is enabled for the website. Due to the limitations of Manilas static rendering implementation only one static render can be active on the server at any one time., if a second is attempted addedValues issues an error.

fc10 - item row detail reports are the report analogy of row update forms; they report on one specified row of row placeholder table. All references to column variables of that row placeholder that are not subscripted are assumed to be taken from that row. The variable may not be qualified with forEach. In all other aspects, the report is an Item Detail report.

fc10 - When an Item Detail report is defined, if the rico library is available, the report contains a forEach qualifier for a multiple valued row place holder variable, and at least one Item Row Detail report exists for that row place holder variable, addedValues will now offer to install rico onClick handers for all column variables of the row placeholder. The onClick handlers direct the output of a Item Row Detail report to a designated place in the report layout, without causing a page refresh