list isn't updated after removal, and requires a page refresh (and therefore relogin) to reflect changes

list isn't updated after removal, and requires a page refresh (and therefore relogin) to reflect changes

enables multiline messages and cached pages to speed up loading

Using an instance of the class from the script create a huge memory leak
in zope which does not happen when instanciating class from the code.
The issue seems to come from the use by the matribox as simple test cases
of instanciation from script do not reproduce the memory leak

It is automatically created and provided by the ondatachannel event listener.
This bypasses some Chrome bugs.

This converts the WebSocket/RTC APIs into renderJS methods.

because inkscape DPI handling differs by its value.

Drop dead code.
Update a few archaisms.
Simplify code.
Improve coding style, reduce indentation.
Escape rendering.

Add support for visibility checking.
Use portal_type accessors, not properties.
Also, original implementation of getDefaultModuleId would get the object,
then its id. getDefaultModuleValue using it, it was getting the object,
then its id, then the object again...
Also, follow naming convention: getters returning documents are named
getXxxValue, not getXxx.

Favicons accidentally got lost in the change.

Reduce fragmentation by aggregating chunks when writing.
Aggregation is controlled by two new properties, chunk_size and
max_chunk_size.
Implement defragmentation.

Code tolerates this with no change.
Allows jumping to an existing relation without having to hard-code
(potentially a lot of) portal types.

Also, do not use getBaseCategoryDict to avoid mutating cached value and use
a set rather than a None-value dict.
Also, access portal_categories from portal explicitly rather than relying
on acquisition.

"to split" is an irregular verb.
Also, drop badly-worded comment.

Accelerate debugging by providing relevant values right away.

getPhysicalPath is too slow to be called this often.
Flush cache on object clone, which is only useful as an after-renaming
event here.

Also, avoid a few single-use variables.
Also, use modern exception raising syntax.

This reverts commit 9668c1a1.

The problem of timezone is more complex.
Since this commit have a side effect of saving and displaying a different date
when Zope runs on a different timezone that what is configured on the field, it
is safer to revert this commit immediately.

we should not call getInventoryList if there is no account_type_to_group_by_mirror_section_previous_period