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

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

- improve css to calendar view

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

if some BTs are too old, the portal type will be missing,
and the portal type wont be found, and the instance wont
be upgraded.

This issue needs to be tested more nicely, but for now,
remove the raise


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

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

--use_dummy_mail_host option was removed in r42905 (always use dummy MailHost while running unit tests).

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

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

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

   so it is safe to not workaround buildout limitation and install it as usual
   egg


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

called directly (with edit() for instance) and override the reference check that
we specifically wanted to do.

This fixes testERP5Security test failures


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

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

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

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

This should fix the _baseGetMembershipCriterionCategoryList errors in trunk,
that are here because no portal types exist for some Simulation Rules:
even without portal types, we can find correctly the document class, and
perform better.


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

(which is in turn given to setDefaultProperties), all properties are
exported so we should check for None rather than checking for the key



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

to portal type classes if possible.

It involves for instance Delivery Builders, that are stored
as Products.ERP5.Document.SimulatedDeliveryBuilder, and are
out of reach of our automatic migration from ERP5Type.Document...


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

to its storage id, default_reference


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

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

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

build mysql-python against mariadb instead of mysql-tritonn-5.0, that can still communicate to mysql-5.0 servers.


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

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

This fixes unwanted calls to _setUpDummyMailHost

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

Constraints portal types



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

broken tests for ZODB Constraints



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

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

Property Sheets on the filesystem matches the ones generated, so
everything should be fine now



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

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

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

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

This time, include as well Property Sheets containing constraints.


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

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

Constraint has been found for a given Portal Type (displaying a
warning is enough in such case) and also fix a typo when displaying
the message


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

Behavior depends on hash orders, hence the success of the migration
test in testBusinessTemplate, and the bad failures at some other places


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

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

- improve view of search results

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

constraints have not been migrated yet, just ignore them for now


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

to tesseract

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

 - do not repeat lxml


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

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

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