Before, it was in Site _local_properties, but as this is stored in ZODB, old
sites would not have this property and would thus not allow to modify it
through 'Properties' Site tab.

Only erp5_trade, erp5_core, erp5_administration and erp5_base for now.

* Upon bt5 installation, install portal_type* items before bt5 {Document,
  Extensions...} as corresponding Portal Type are required once they have been
  migrated to ZODB Components.

* Likewise portal_{property_sheets, types}, portal_components must be created
  automatically *before* installing any bt5. This is required when Products
  will be migrated but also for bt5 items before bootstrapping erp5_core bt5.

* Set Permissions in ComponentTool instanciation and revoke all permissions,
  then allow only some of them for security sake.

* When creating ERP5 site with unit tests, add ERP5TypeTestCase to Developer
  Role ASAP so that there is no Permission issue when installing bootstrap bt5
  and test bt5s containing ZODB Components.

This will not work when there are several nodes anyway, so just display a
message to the user instead.

Also, upon installation of bt5s, install WorkflowItem before Components as it
is needed to restore history.

Another solution would have been to validate() ZODB Components automatically
upon bt5 installation but it would mean losing 'modified' state information
and also imply that *all of them* will be validated even if a developer wants
to publish non-validated ZODB Components.

getattr() will never load the Component, whereas import does. Also, unit tests
were passing with this bug, so improve unit test so that asserting that a
module is importable does not have side-effects.

For now, just ignore it but it may be required later to define dummy accessors
so that the registry and Components can be loaded even when their accessors
are not generated yet.

It is exactly the same at the end but the name of the latter does not make
sense in this context. Moreover, it allows to get rid of Base import.

If PATH environment variable is not defined, this Products cannot be
imported. Followup of 399f95f9.

banking bt5 which override z_catalog_stock_list.

Just copy z_catalog_stock_list.xml as the new Z SQL method in banking bt5 as
it does not make sense to have more than 300 Inventory Lines in this case.

performance reasons, so fix improved listbox sort feature accordingly.

This fixes testFunctionalCore failures.

Also, remove copy and paste code from DCWorkflowGraph in ERP5Workflow and
allow to override getPOT() like ERP5Workflow does.
Signed-off-by: Arnaud Fontaine <arnaud.fontaine@nexedi.com>

.prop() is available after jquery 1.6.

The issue is occured when using inventory document with inventory cache.
Add a test case to make sure this issue has been solved:
  testInventory#test_18_InventoryDocumentAndInventoryCache.

Replace a zsqlmethod for translated_simulation_state_title with python script to add an extra condition to where expression. This helps m
ysql optimizer to make a better plan. Without it mysql optimizer may make a bad plan to join catalog and translation and causes bad performa
nce problem.

This reverts commit 70a8e561 because this
changes is about improving the performances of Accounting Transaction Module
not used in this project. Moreover, this change would required to reindex
Accounting Transaction Module.

Conflicts:
	bt5/erp5_configurator_standard/bt/revision

Use IPAexGothic to make sure that Japanese is displayed properly. Also, make
sure that all the files are properly closed even if an exception occurs thanks
to 'with' and 'NamedTemporaryFile'.

Fix an inventory bug. When there are more than 300 inventories which are cancelled by inventory document, inventory document creates wrong stock records.

Fix incorrect change of my_view_mode_quantity ProxyField which must point to Base_viewFieldLibrary/my_view_mode_quantity so that figure CSS class is applied (9fcbe9c1).

To apply this change on existing on existing table:
ALTER TABLE stock MODIFY order_id BIGINT UNSIGNED

Before, when creating new full inventory Document, resources which are not
present in new Inventory Document were simply ignored. So, new movements were
added "manually" with quantity less than or equal to 0 to workaround this
issue.

New inventory fixes this issue so that this workaround is not needed
anymore. Temporary movements are created for resources not present in new
Inventory Document and added to stock table (through z_catalog_stock_list Z
SQL Method) with uid equals to Inventory Document UID.  However, the primary
key on stock table is (uid BIGINT UNSIGNED, order_id TINYINT UNSIGNED), thus
when there are strictly more than 255 temporary movements, order_id overflows
because the max value of TINYINT UNSIGNED is 255 and MySQL sets order_id to
255 after the first 255 temporary movements (as strict SQL mode is not
enabled), thus raising an IntegrityError later on because of duplicated
entries.

erp5_simulation should not be required for erp5_trade and erp5_accounting as some system do not use simulation.