• last updated 16 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Perform a full initialize on both packages to get ::xo::cc initialized

prefer call of "pretty_link" on package_id to avoid suprises on pages from shared locations

factor out common code

make listing more compact

Port reform that replaces publish status display from a png to a character + css style to the xowiki/admin/list

The behavior of the default table widget had to be adapted to reflect that of the bootstrap one: css class from the line is appended to that from the field definition

  1. … 1 more file in changeset.
use "throw" in exception handling with "try"

Fail with the actual error message when parsing the value fails, rather than because of "result" variable not being set

still initialize array

improve comment.

since "nsv_get $array $member varname" returns 0, when the array does not exist, we do not need the extra value for initialization

cache parsed form_constraints via nsv instead of via global variable

- Define converters as procs

- Register these procs as aliases where convenient

- this effects:

dict_to_fc, dict_to_spec, spec_to_dict, fc_to_dict, dict_value

- extended regression test

- bumped version number to 5.10.1d9

minor editing changes

improve location of comment

prefer "Package require" over "Package initialize" when possible

adjust code with regression test, which performs literal comparison of rendered content

    • -3
    • +3
    ./tcl/test/xowiki-admin-tests-procs.tcl
reduce verbosity

Make error consistent with the already existing check in the content-repository

Handle more gracefully the case, which should not happen on a production system, that the file being downloaded does not exist on the filesystem

- deactivate unused link-templates

- make quoting of label more consistent (it is passed in already quoted from the rich-text editors)

- whitespace changes

support link rendering in pages, which are not yet prepared for display

support renaming of autonamed entries

previously, it was not possible to rename autonamed entries via edit form.

now this is allowed, and item name validation is more robust, support

functions return meaningful error in unexpected situations.

Added archiving of items, reduced usage of images for icons

When an item is archived, it is not shown to plain users. Internally,

when an item is archived, the publish status is changed to "expired"

and removed from search/syndication. When an item is archived, it can

be brought via "toggle-publish-status" to state "production" again.

Future versions might rename the item in such conditions, but

currently, it is NOT renamed, so one cannot create one more item in

the same folder with the same name.

For realizing this functionality, the includelet "form-usages" accepts

now an additional optional value for "-buttons" named "archive". The

publish status toggle can be used now for switching from

"production"->"ready", "ready"->"production" and

"expired"->"production".

Additionally, the usage of .png images as icons was reduced by CSS

elements for easier styling (e.g., for different themes) and for

reducing less server requests and better responsiveness. In particular

the images for active.png and inactive.png are not necessary any more

and were removed.

Bumped version number to 5.10.1d8 to enforce loading of the message

keys.

    • -8
    • +25
    ./www/resources/xowiki-yui-specific.css
white-space changes

solve property resolution in form-usages by avoiding lookups from the current item to reduce side effects

CVS: ----------------------------------------------------------------------

fix form field property resolution: in form-usages, default values were overruling the specified properties

define javascript input handler for formfield class numeric to prevent non-numeric input while preserving the multi-lingual interpretation

Update jquery-ui to version 1.13.0 to mitigate high severity XSS vulnerabilities

    • -11
    • +15
    ./www/resources/jquery/jquery-ui.css
    • -740
    • +1080
    ./www/resources/jquery/jquery-ui.js
    • -10
    • +3
    ./www/resources/jquery/jquery-ui.min.js
Fix the branch performing get_page_from_item_ref when multiple parent_ids are specified, rename the loop variable so that the original argument is not lost

Use a trivial lookup: content::item::get might perform many queries, in particular on success