Fix: use portal type while fetching data, instead while setting.
Protect: ff no custom_trade_condition is found, raise loudly.

Also, reduce the scope of one more try..except block.

Also, there is little chance for a valid user UID to be None (or a string).

Only next two months are covered.

Create only for two months in advance.

This reverts commit b590542d.

Conflicts:

	master/bt5/vifib_erp5/bt/revision

Applied Rules are generated later.

Expose missing test features.

Builders are called globally, so deliveries are appearing earlier.

Rules have a bit more complex applying logic.

Conflicts:

	master/bt5/vifib_erp5/bt/revision

variation property which comes from Item generates getVariationPropertyList.
VariationRange's property defines variation_property which also generates
getVariationPropertyList

As there is conflict which is not solved by category accessor generation
sorting (which is per property sheet) adding later VariationRange will result
in overwriting accessor for category with own one.

Conflicts:

	master/bt5/vifib_base/bt/revision

Conflicts:

	master/bt5/vifib_base/bt/revision

Conflicts:

	master/bt5/vifib_data_simulation/bt/revision

Message was: <ERP5Type.ConsistencyMessage for PropertyTypeValidity on
    web_site_module/hosting (message: Attribute layout_additional_css should be
    of type string but is of type <type 'tuple'>)>

Conflicts:

	master/bt5/vifib_erp5/bt/revision

Conflicts:

	master/bt5/vifib_erp5/bt/revision