git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41641 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41640 20353a03-c40f-0410-a6d1-a30d3c3de9de

* ERP5Type.PropertySheet becomes a dynamic module that returns strings
  instead of classes for compatibility:
  - the document classes can now use strings in property_sheets attribute
  - if a document uses a string instead of a class reference to point to a
    property sheet, it means that the property sheet can either be an old
    (filesytem, local, in a product) property sheet, or a zodb propertysheet

  For now, the contents of ERP5Type.PropertySheet (strings) are overwritten
  if a local PropertySheet is loaded from the disk. But with time, as
  property sheets will migrate to ZODB, the module will empty itself and
  contain only strings.

* Move all property sheets from all products to ERP5PropertySheetLegacy
  product. Only property sheets that were left 'as is' are CMF* property
  sheets.

This commit is mostly a move to another Product, and should have small
consequences on tests/existing instances.

However, if you used to import PropertySheets in custom/project code
in your custom Property Sheets, you will need to rename:
   from Products.*.PropertySheet.Foo import Foo
to:
   from Products.ERP5PropertySheetLegacy.Foo import Foo



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41639 20353a03-c40f-0410-a6d1-a30d3c3de9de

sure that aq_dynamic will know where to find the property sheet


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41638 20353a03-c40f-0410-a6d1-a30d3c3de9de

  if it is present overthere (otherwise, it is likely a property sheet
  in ERP5PropertySheetLegacy and it will be loaded by aq_dynamic)
* comment as to why Solver Tool is one of the exceptions
* LOG when Property Sheet Tool is missing



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41637 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41636 20353a03-c40f-0410-a6d1-a30d3c3de9de

are not broken while migrating to ZODB property sheets


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41635 20353a03-c40f-0410-a6d1-a30d3c3de9de

propertysheets and constraints


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41634 20353a03-c40f-0410-a6d1-a30d3c3de9de

comment for now this code until proper solution is found

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41632 20353a03-c40f-0410-a6d1-a30d3c3de9de

this allows to go further than the default limit to 1000,
and this fix unit test failure

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41631 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41630 20353a03-c40f-0410-a6d1-a30d3c3de9de

This fixes testLegacySimulationOrderBuilder

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41629 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41628 20353a03-c40f-0410-a6d1-a30d3c3de9de

such as Variables, References, Charts, Fields.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41627 20353a03-c40f-0410-a6d1-a30d3c3de9de

Other checks regarding image size assert that Image is still well replaced.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41626 20353a03-c40f-0410-a6d1-a30d3c3de9de

Take into account this behaviour.

Before refresh:
  <text:reference-mark-start text:name="week"/>
      <text:span>Monday</text:span>
    <text:reference-mark-end text:name="week"/
After refresh:
  <text:reference-mark-start text:name="week"/>Monday<text:reference-mark-end text:name="week"/>


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41625 20353a03-c40f-0410-a6d1-a30d3c3de9de

calling getProperty?key= in the URL does not work when psyco is installed, so use an intermediate python script

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41624 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41623 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41622 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41621 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41619 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41618 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41617 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41616 20353a03-c40f-0410-a6d1-a30d3c3de9de

Do not try to run this test if urlnorm is not available


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41615 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41614 20353a03-c40f-0410-a6d1-a30d3c3de9de

if given url is not valid.
keep AttributeError catching for legacy


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41613 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41612 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41611 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41610 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41609 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41608 20353a03-c40f-0410-a6d1-a30d3c3de9de

because connection string might use ':' in order
to specify port numbers

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41607 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41606 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41605 20353a03-c40f-0410-a6d1-a30d3c3de9de

Add specilized trade condition
Remove annotation
Update returned url when check paypal payment


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41604 20353a03-c40f-0410-a6d1-a30d3c3de9de

ZMySQLDA connector for the activities database would finish its
commit procedure before ZODB, making the description of an activity
message in MySQL available before its respective data in the ZODB.

The fix consisted in replacing the ZMySQLDA connector with another
one based on ZMySQLDA but with a “sortKey()” method that forced it
to be sorted after both the ZODB connection and the ZMySQLDA
connection for ZSQLCatalog.

Analysis of issue was done by Sebastien and Julien.

This patch itself was done by Leonardo.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41603 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41601 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41600 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41599 20353a03-c40f-0410-a6d1-a30d3c3de9de