true is not an allowed value, causing a visible problem tabSize to be
ignored on empty documents and using 4 for python.

   Prevent the user start an inconsistent assignment, since, extra property sheets can include some
   business logic around assignment configuration.

This fixes a regression with 445e8fa8 (ERP5TypeTestCase: rework
default manager password generation, 2024-05-27), it was no longer
possible to run live tests from a "normal" zope instance, this was
failing with:

Traceback (most recent call last):
  File "./eggs/Zope-5.10-py3.9.egg/Testing/ZopeTestCase/PortalTestCase.py", line 59, in setUp
    self._setup()
  File "./parts/erp5/product/ERP5Type/tests/ERP5TypeLiveTestCase.py", line 156, in _setup
    self.login()
  File "./parts/erp5/product/ERP5Type/tests/ERP5TypeTestCase.py", line 290, in login
    return PortalTestCase.login(self, user_name)
  File "./eggs/Zope-5.10-py3.9.egg/Testing/ZopeTestCase/PortalTestCase.py", line 146, in login
    user = user.__of__(uf)
AttributeError: 'NoneType' object has no attribute '__of__'

It was only possible from a runUnitTest instance.

This comes with a small breaking change that when using file:// URLs,
they need to be well formed ( file:// + path and not file:/ + path )

Use scrubHTML() from safe_html module instead.

It was using bytes(), but this seems wrong now.

a17bb910: py2/py3: Make Products code compatible with both python2 and python3.

erp5_syncml: invoke callback method by activity in non split_indexation case as well to make transaction shorter.

Use the removeProperty method.

This executes even if setup() encounters an error and the cleanup hook is added
when opening the file, not later on.

Also, unify makeFileUpload() and makeFilePath() to remove duplicated code.
Co-authored-by: Arnaud Fontaine <arnaud.fontaine@nexedi.com>

See merge request !1979

- {'destination_list': ['person_module/he', 'person_module/me'],
+ {'destination_list': ['person_module/me', 'person_module/he'],

See merge request !1963

   The script is supposed to be called on portal context (or any context) and not on MailevaSOAPConnector, and it should return a MailevaSOAPConnector for a given reference.

    In the implementation where the user cannot directly insert holidays (by an specialised role/implementation) it allow the accountant insert the values more easily. Using a simple action.

    Add simple jump for navigate to the holidays/leave

  This helps to review value on the print out

See merge request nexedi/erp5!1959

Fix UI tests error introduced by f159d4f2. As it checks for timeout,
simulation finished state cannot be reached anymore.

Fix projection by not making a square map from non square limits (width != depth).
This way rotation does not result anymore in deformed shapes (it was the case until now because proportionality was not respected between width and depth).

Fix typo (cbe50b0f): erp5_accounting_l10n_fr: the French Fiscal Report (FEC) can be generated for different ledgers.

WebSection.getDocumentValueList() returns absolutely all the documents (as catalog brains) reachable by the web section. Then, calling .getUid() on them load all the objects in memory. The number of documents is of the order of hundreds, even on a small ERP5 (web pages, web scripts, etc.).

Limit the documents to retrieve in WebSection_getLatestDiscussionPostList by filtering on the portal_type, and do not load them needlessly in memory.

  This aims to add compatibility with BTreeFolder2 API, even it is not
  required. Since some checkConsistency may call self._cleanup() regardless
  expecting that the folder is a [H]BTreeFolder2 always.

  This was detected when a post upgrade constrant was included to
  portal_categories

The methods used in indexing did not make a difference between the case
where the price is None (ie. price is not set) or where the price is
set to 0 - in both cases this was saved as NULL in stock.total_price
column. This is incorrect, we need to keep the distinction between
these two cases also for inventory calculation.
We had some places where we select IFNULL(stock.total_price, 0) to work
around this, we don't plan to change the existing ones for now, but
while discussing on !1974
we concluded that a newly idenfified case of a problem consequence of
these NULL should be handled by fixing the indexation. To benefit from
the fix, impacted instances will have to reindex documents present in
the stock table with stock.total_price is null.