After that change, when there is a movement from A to B in **started** state, `Item_getCurrentSiteValue` will consider that this movement has already reached B.

Before this change, `Item_getCurrentSiteValue` was returning None, which somehow makes sense because started movement is in transit state, so the item has left A but not yet reached B, so it is in an unknown location.
Low level current tracking list API ( getCurrentTrackingList ) does not return items for started movements.
Honestly, I do not know if this is by design. (  anybody knows ? )

I will work on adding missing tests, but please tell me if I am wrong in thinking it should return None.

@gabriel @rafael @tb @tc do you remember why this change was introduced ? Maybe that behaviour of returning None should be only at the level of `Item_get*` scripts ? 

/reviewed-on nexedi/erp5!70

Hey @romain, I noticed default to now was not implemented in renderjs ui.

Here, I implemented it server side to be consistent with erp5_xhtml_style ui where default to now is in server time zone.

/cc @gabriel 


/reviewed-on nexedi/erp5!73

Documents are by default sorted by modification date to ease user search.

my_start_date field has default to now enabled, so it does not have ""
as default value

we need erp5_configurator_standard_trade_template business template for
default_delivery_rule

This is a follow-up of commit 8712c638
which fixed the following case:

  A  B  C  D    # transactions
  r  r
     A  r  r
        R1 R2
           A3

where A stands for Append, R for Rotate, and uppercase for conflict resolution

  A3 contained duplicated elements from both R1 & R2 (those added by B)

This commit fixes the same issue during rotation:

  A  B  C
  a  a
  A     r
     A  R
        R

  (elements added by A were duplicated)

from erp5_core to erp5_forge.
Also, rename field from my_repository_list to your_repository_list.

/reviewed-on nexedi/erp5!74

To me, it seems a bit strange from user experience point of view to have suggestions for what login / password to use.

/reviewed-on nexedi/erp5!67

fixup! Movement: Add isMovingItem method to be possible check if the object is moving physically or not

Delivery Cell follow the same logic as Deliver Line to decide if a
movement is moving item. There is no "Delivery Movement" class yet, so I
duplicate the method for now.

Without this fix, item tracking no longer work when using variations.

Just use erp5_default_business_process as specialise so that expand does
not fail and we can still have item management tested until test suite
is fully updated for new simulation.

More complex tests that deals with divergence are left as
newSimulationExpectedFailure for now.

fixup! ListBox: support rendering empty item as user's input in multi item widget having default values.

fixup! ListBox: support rendering empty item as user's input in multi item widget having default values.

This is currently required for NEO.

so that it follows naming convention ('To' is a closed-class word and should not be titlecased)

This reverts commit 0168bf60

/reviewed-on nexedi/erp5!69

where the actual Python code or Test content is exported separately from the xml metadata

to use content_type or reference even if the object is broken.

to the Portal Types for which the data
is exported separately to the meta-data.
Tests added to testBusinessTemplateTwoFileExport.py

testTemplateTool.test_revision: Change hard-coded hashes. test_core file structure has changed since SkinTemplateItem/portal_skins/erp5_test/test_file has been separated to two files

All business templates migrated to new format with files like Python Scripts, Web Pages, Web Scripts etc. separate to xml

erp5_web_renderjs: Set init script for Web Script and Web Style so that it sets content_type as 'text/javascript' and 'text/css' respectively

erp5_core: TemplateTool: Add a view in import/export dialog, so that migration to new format can be automatic

TemplateTool: importAndReExportBusinessTemplatesFromPath renamed to importAndReExportBusinessTemplateListFromPath