Fix a bug when enabling a site on a new server; work around bad
address in a forms testdata setup if encounteredStatically rendered search forms sometime failed because there were
no pathargs defined. for the url Fixed. A bug in the validate method for a string variable with a URL value
required the presence of the regex DLL: not always a valid
assumption. Now re is used preferentially as for every other case. When a form is submitted; if the submits don't validate the form is
presented again with the input values and appropriate error. If the
form contains wysiwyg elements; the 2nd presentation of the wywiwyg
did not function correctly. This change ensure the forms are
functional after an error. the addedValueMacros.countryNationality macro did not report
Egyptian for country EG (Egypt). Fixed. A new virtual builtin variable gemsFolderName has been implemented.
It returns the path to the folder where the website manila Gems are
stored. The rssLinkURL macro erroneously inverted the order of the node names
rss and public in the link url when the site had static rendering
enabled, but the link in question cannot be static. Reports with an updater, were not able to revert to having no
updater. Now the dropdown allwos this option. The HTMLArea3 wysiwyg variant soemtiems failed wiht a message
complaining about "coercion of a string to a number". Fixed. The searchprefilled macro sometimes failed with the message "the name
"flForceGrouping" hasn't been defined.." Fixed. In demo mode, the layout of forms wasn't visible. Fixed. The messages builtin variable sitestructurepath now supports the
within operator in queries, even though the sitestructurePaths
variable may not be indexed. The within operator performs a "walk"
through the site structure until it locate the directory (category)
of the value of the right hand side expression, and then returns each
story in that directory as a hit. The right hand side must evaluate
to a valid path. Because this is not using an index, the search
times are not as independent of the webiste size; some searches may
be quite slow by addedValues standards. The case of the path nodes is
not significant. You may not use siteStructurePaths in search forms,
but you MAY use a a Search limiting Query (preferably before) to
constrain your search to a specific directory within the site
structure.
example from addedValues.org site siteStructurePaths within "/faqs/". In sites with macroxref preference enabled; dumping a schema left
references to message numbers in reports , which were invalid in any
website where the schema was loaded. Fixed.
-- - David Bayly. Programmer and digest reader. dbayly at udena dot ch
Digest Readers do it once a day.
|
