romain_dev: forum

romain_dev: forum use html viewer

romain_dev: forum improve post rendering

romain_dev: thread reader use page language inqtead of local

romain_dev: forum set expected link on the listbox cells

romain_dev: thread fixup

romain_dev: thread use line separator instead of background color

romain_dev: thread paginate

romain_dev: forum link to last page

romain_dev: thread simplify conf from erp5form

romain_dev: forum attachment

romain_dev: thread force white background

This reverts commit e50d05af.

Do not access form submission REQUEST from the listbox list method,
as it is rendered asynchronously in ERP5JS

Allow edition in the new UI

This make everything slow as hell and prevent to quickly save.

Example: <h2 class="foo">bar</h2> => <h3 class="foo">bar</h3>

erp5_web_renderjs_ui: keep previous focus color

If user group are recalculated before changing the workflow state, it will only return the same security group
See nexedi/erp5@c00c3636

Accounts with a balance that is not 0 in transaction currency
(quantity) and 0 in accounting currency (asset price) were not correctly
indexed in balance transactions.
The visible problem was that every year the amount in local currency for
this account was doubled - while the amount in accounting currency
remainded 0, making this problem not so impactful.

When an invoice has a resource set, newly added invoice lines and cells
will lookup prices using currency exchange lines (and might even find
a price).

uninstalling a ModuleTemplateItem containing document is usually not
what people want, so the default option should be to keep.

See merge request !2063

Commit a01da084 failed to fix the
handling of parameters in the dealShebang function and the bug is now
triggered since slapos@f834a06f:

$ PATH=...  SLAPOS_TEST_LOG_DIRECTORY=... SLAPOS_TEST_SHARED_PART_LIST=... /bin/sh '-e
' /srv/slapgrid/slappart0/t/.../i/0/bin/runTestSuite ...
runTestSuite: /bin/sh: 0: Illegal option -

The script now has a drop-in replacement in `erp5_trade` which works as-is even
in the case of advanced trade (calls `Movement_isQuantityEnabled`). Henceforth,
the custom script in `erp5_advanced_trade` is not needed anymore.

The two scripts were a bit too independant from one another, sometimes causing
weird behaviours. Editing a quantity now depends on the quantity being enabled,
which happens when the line is not expected to have cells or sublines.

Also enforces expected behaviour for items: if a product or service has
*required* items, its quantity cannot be edited, since quantity of the items
should set the quantity of the line or cell.

New year does not mean the period is 365 days.

See merge request !2057

   The alarm was replaced by a proper CodingStyle test. Fixit is incoherent since you need to edit/custom it to adjust the cache plugin for each use case.

   Rely on test result is just fine for this purpose.