(Sorry, sent too son. Fixed the typos and put bug fixes under that
heading and new features under its heading!)Don't forget to run addedValuesPi.Install() after the update if you
wish to use the new custom renderers and post processors in this
version. New Implementation. - a builtin global variable gemsFolderURL returns the configured URL
that contains all gems in the site. - a builtin global variable isStaticRendering returns true when a
page is being rendered statically. - 8 new message builtins variables have been added to provide read
only access to fields maintained by the commentIt manila plugin; the
main purpose was to allow the total number of comments to be accessed. - previously the getValue macro rejected attempts to access member
variable values for designated member keys , unless the page was
accessed by an editor. This restriction has been lifted, the status
of the person viewing the page is no longer a factor. The change was
made because the site Managing editors control the macro calls, so
security is preserved. Likewise, the page macro imposed similar
constraints, now lifted. - wysiwyg editors are incompatible with javascript checks for
required form elements (at submit time), now addedValues checks such
for elements on the server side only. - addedValues now defines a system cohort Administrators , in every
Manila website. A member of a website is in Administrators if they
are also a member of the admin website. - several new custom renders provide a dropdown menus to choose one
ro more of some Manila capabilities, including Mania themes,
addedValues dumped schema, Manila supported languages , Manila
registered plugins and the names of entries in the variants sub-table
(if it exists) of a postprocessor table. these will be available
only after addedValuesPi.install has run and they have been enabled
in he addedValues controlpanel in the admin website. - a new post processor allows user transactions to create new Manila
webSites using a beginUserTransaction macro call and a tailored
form, similar to how Manilas hostingSuite.createSiteForm macro works,
but with the ability to set the website home page url as you wish,
install plugins , load an addedValues schema and cater to variamt
webistes. An example will be forthcoming on the addedValues org
website. Bug fixes - if a query has parameters, pages calling it with
addedValuesMAcro.query cannot be statically rendered. This is now
enforced. - the deleteplaceholderrow entry point in the website was restricted
to editors only, which meant members could not use forms to delete
rows from tables they owned. Fixed. - obscure bugs in indexing builtin column variables were fixed. - the message builtins variable responses , had an incorrect default
value. Fixed. - a bug deleting a group ("the name "adrSite" hasn't been defined") was fixed. - the error message when a query is called specifying a non-existent
report was improved. - obscure errors in hierarchy path variables methods for non text
indexed case were fixed. - the error message logged by the delete message callback error
recovery was made more explicit. - another excess entity encoding in urls as generated by
addedValueMacros.serveReportURL was fixed. - the tineymce wysiwyg package did not work correctly in websites
whose home page url included a subpath. Fixed. - in sites where the home page url which had a non empty path; the
rico urls were not constructed correctly.Fixed. - some flavors of variables failed on storing a value if a string
maxlength was set. Fixed. - testing a query with reports that used the ability to jump to
random fits failed, as the url was set incorrectly. Fixed. - a password form element rendering always set maxlength to 0,
making the field useless. Fixed. - when testing user transaction forms, re-display with values from a
previous post would "hot up" textarea form elements. Fixed. - the custom renderers RSSreporNames, siteCohortsMultibox and
siteTemplatesMenu built menus with a name attributeof option tags,
instead of value. Fixed. - before calling onclick reports and forms, the server side
addedValues routines that handle Rico calls, now hides the searchargs
used to communicate between the rico library clientside and
addedValues serverside. This fixes some obscure bugs when the onclick
report calls a query. - a bug in the parser handling of var1 = related(var2) where var1
and var2 are both multiple valued, was fixed. Known issues - none. Enjoy!
-- - David Bayly. Programmer and digest reader. dbayly at udena dot ch
Digest Readers do it once a day.
|
