• last updated 7 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Extended functionality of the DropZone widget

- added parameters "label", "disposition" and "file_name_prefix"

for better configurability

- added support for updating the current page with feedback of the

dropped files. This is used e.g. by the online exam in the exam

protocol to display incrementally thumbnails of feedback files.

- change property "uploader" to "disposition", since "uploader" is

somewhat ambiguous. "Disposition" defines, what happens after the

file was uploaded, e.g. whether the content has to be transformed,

etc.

- bumped version number to 5.10.1d35

  1. … 2 more files in changeset.
fix typo

use bootstrap table renderer inside includelets for bootstrap3 and bootstrap5

moved included stuff from xowiki/www to xowiki/lib

Generalized handling of local_return_url

I am not fully happy with the handlings of "return_url" in exam workflows.

Maybe this can be reworked in a way such that "local_return_url" is not

neccsessary in the future.

Test behavior of the omit formfield spec

Improved support for composite questions and bootstrap 5

This fixes a bug when composite questions were generated with

bootstrap3 and rendered later with bootstrap5.

  1. … 1 more file in changeset.
improve bootstrap5 compatibility for inclass exam

  1. … 1 more file in changeset.
Preliminary cleanup

In this test we will loop through instances of ::xowiki::Page currently in memory to perform some checks. When multiple tests run in the same request, we cannot guarantee that other tests won't create ::xowiki::Page instances that won't comply with the conditions here. We cleanup any existing object in advance to start from a clean slate.

Skip processing for all formfields that are defined as disabled:

the browser should not send us these data in the first place.

Extend test: show that even when a field is defined as disabled, a request crafted to carry these fields will get through and the values will be stored

A fix will come shortly, similar to what was done for compound fields

undo part of last change

unfortunatly, the 0.9.3 issue can't be fixed so simple as hoped. The "-html" flag is necessary for dealing with autoclosed entries.

for orthogonaly, remove "-html" flag from dom parse to avoid a potential top-level <html> element

fix compatibility with tdom 0.9.3

fix warning (including some false positives) in regression test

  1. … 4 more files in changeset.
we need the upgrade script, since the automatic aler just kicks in, when the constraint does not exist. Antonio was right.

Nevertheless, it would be a nice feature, if the ORM would handle this.

remove useless upgrade scripts (xotcl-core does this automatically on reloads)

Document and enforce expected behavior when Forms are deleted: this is forbidden and returns an error as long as they have instances

Follow up of https://cvs.openacs.org/changelog/OpenACS?cs=oacs-5-10%3Agustafn%3A20220622174910

In the end we need the upgrade logic, as the ORM will kick in only if the column is just being created

  1. … 1 more file in changeset.
Make page_template foreign key deferrable

This solves the problem of deleting implicitly child-items, which

depend on each other when deleting an item. When deleting an item, the

deletion of child-items in the content repository happens in an

arbitrary order, which could raise fk constraints. Since the deletion

happens in a transaction, the deferring checking of the constraints

helps, since then the constraint violating item is also already

deleted.

There is no update script necessary, since reload alters the

constraint.

undo recent change, which is not sufficiently general (and solve the issue by db means, next commit)

Address the cornercase of form pages having their template stored in the same folder: when deleting items containing such a setup, cleanup these formpages first

Addresses a consequence of https://cvs.openacs.org/changelog/OpenACS?cs=oacs-5-10%3Agustafn%3A20220613165033

remove traces of md5::md5, since ns_md5 is emulated also for AOLserver

  1. … 2 more files in changeset.
Drop "ON DELETE CASCADE" on page_template, since this might lead to crippled entries in the database.

When someone delets via operations in the database a form, protentially existing

form pages refering to this item might be left in a crippled state.

The cascade operation deletes the revision (xowiki_page_instance), but leaves

the half-crippled item. The problem does not exist over the web interface,

since it does not allow such items to be deleted while form pages exist.

  1. … 1 more file in changeset.
Add support for menu-entries, where simply a "-link" is provided

Provide a fix for "dom parse -html ..." for adp tags.

"dom parse -html" has two problems with ADP tags like "<adp:icon ...>":

a) If the tag name contains a colon or underscore, the tag is

treated like plain text, i.e. "<" and ">" are converted into

HTML entities.

b) These tags have to be closed "<adp:icon ...>" is invalid.

Several existomg ADP tags have not closing tag.

Therefore, we resolve the ADP tags before parsing the text by

tdom. There should be some future framework support to do this in

general, but until we have this, resolve this problem here locally.

New method "marshall_all_to_file"

This method is similar to "marshall_all", but exports the objects

directly to a file. This can save memory when exporting a large

collection of objects, since the plain "marshall_all" appends to

string, which can get very large, especially due to Tcl's

"double the size when space is needed" policy during "append"

operations.

fix for old-style ad_form based forms with radio or checkbox controls for bootstrap 5

These controls were used with a bootstrap3 classes, which had the consequence

that no input was possible for these fields. Probably, similar changes

are as well necessary in other situations as well.

fix typo

tdom sometimes html-escapes unknown tags

Consider code like

#

# dom parse -simple -html $form doc

# ...

# return [$root asHTML]

Unfortunately, this causes that some tags unknown to tdom

(like <adp:icon>) are converted to escaped tags (&lt; ...).

This can be regarded as a bug. To avoid this problem, we

substitute here the adp_tags in advance. This needs more

investigation in other cases.... The potential harm in this

cases here is very little, but probably, there are other

cases as well where this might harm.