Use SaleOrder_viewAsWeb instead ad-hoc name.
For e-commerce, we do not allow user edit his own order on web mode.

Use erp5_ui_short cache on Products List

The layout was moved to appropriated business template

erp5_commerce should only contains core implementation and nice widgets for implement erp5_commerce.

Consider that view is the default is wrong, we should invoke call on the object, this change fix listboxes used on frontpage of a website.

Reference should be used for internal purpose (map with PayPal for example) and Title should be a fashionable name.

Make ID editable (by Manager) since this is useful quite often to prepare a business template with initial data of an ERP5 site. Items are ordered in a way which is similar to DMS.

Sale Order and Sale Order Module should have a default web view in an online shop.

Also improved comments and docstring including TODO.

Also improved comments and docstring including TODO.

Also improved comments and docstring including TODO.

Also improved comments and docstring including TODO.

Also improved comments and docstring including TODO.

Group, site and function are set in ad-hoc yet appropriate way. These scripts should be considered as examples or removed and merged into generic ERP5.

Support variation and size categories. Generic implementation required in future.

For now variation and size are hardcoded (in listbox). This should be changed to use generic code based (for example) on a dynamic definition of columns.

A resource image can be defined in the Resource itself or in its variations. The easiest way to test if any image exists is to try to get its URL.

Use request (populated by site template) or current context to determine the web site. Also cleaned some comments and docstrings.

This script creates a context to compute the default price of a product in the online store in line with extended getPrice API

and add a comment to explain deprecation.

Current predicate category table is not filled enough with children nodes and will thus not
select everything it should.

Added comments about mixup of kw params in Price API.

This method is intended to use when we are disabled 'Store in the ZODB'
or set a big number as the 'Store interval', but at the same time we need to
update the persistent dict from the fresh portal_ids table at a certain point.

This method needs a unit test.

So that we can get all the records of portal_ids table even when there are more
than 1000 id_group on the table. The ZSQLMethod was not intended to limit to
retrieve the records.
Of course it is better to get the records more gracefully like first getting
0..999, then 1000..1999. For now this is acceptable.
(Confirmed by Sebastien)

Do use catalog when switching between different tabs to avoid having to deal with objectValues / contentValues API. Avoid use cases when a Pad may contains many Boxes.