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.

They use the same method name to do another task: check consistency on passed
object. Thus it is impossible to check consistency on them.

They use the same method name to do another task: check consistency on passed
object. Thus it is impossible to check consistency on them.

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.

For now check functionality of variation_property_list property.

Reuse searchAndActivate method.

Allow to select no modules, which will result in full, unrestricted site check.

* move create/drop table SQL for content_translation table from erp5_content_translation to erp5_full_text_*_catalog BT.

revert 5389ed8c (use countResults as a count method for a listbox where we use portal_catalog as a list method).
'countResults' method is overridden in Document/ExteralSource.py and using 'portal_catalog' as count method is internally translated to 'countResults', thus using countResults globally here may cause unexcpected value for certain cases.

Based on a patch by Aurélien Calonne <aurel@nexedi.com>.
Also, cleanup TranslationProviderBase code a bit.

This fixes a regression by commit 6fd63363.

This is similar to commit a0d26594
("Fix possible resource leak with ImageMagick conversion").

There should be no need for volatiles, as this class doesn't subclass
Persistent. Also, TM interface is deprecated.

They are much easier to understand than ngt, max, etc.
There is no replacement for minngt and minmax at this time, though.

This prevent using iterators, and there is an easy alternative.

The TestPage_view was lacking of several fields important to DMS/Web usage of the files.

This reverts commit b7677ac0.

More analysis have to be done before changing implementation.

Business Link method accepts None, so allow to call global build on Business
Process itself.

Show appropriate informations, for now use Base_viewDict is enough to show internal dict. In future we might filter atributes and/or create some convention.

This method requires a serious refactor to fix the progress bar
at Configurator.

Configurator Key is a legacy.

Configuration Key is a legacy from Previous design and it looses their need. If required the design should contains an better implementation.

sign should be mandatory and its default should be payment transaction group's value in PaymentTransactionGroup_viewSelectPaymentTransactionLineListDialog.

Commit aa8e9a60 broke testBusinessTemplate

This reverts commit e1bd6f47.

Encapsulate month frame in same month instead of overlapping next one.