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

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

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

This method will help caching handling by checking
that cached conversion result is computed from same data
as the one carried by document.


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

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

of the returned filename


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

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

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

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

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

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

fixed by revision 35192 (wrong sql connector used by Id tool)

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

index_html method for a proxied PDFDocument 


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

was a mistake to use cmf_activity_sql_connection.

because of the wrong connection, and because id tool is doing
commits in the middle of transactions, rollback commands from
CMFActivity were not working. This can ends with inconsistent
activities

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

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

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

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

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

Revert revision 35129. Previous decision was wrong. We should not change the place once we publish it. And also there is no new payment rule yet, then no reason to move it to legacy.


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

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

Refactor development configuration for make runUnitTest and developement independendt. For run tests the instance is not required.

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

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

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

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

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

we need to calculate first causality in test() too, but the expected behaviour of this movement group in delivery level is unclear.


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

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

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

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

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

use class variable for credentials of publish method.


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

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

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

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

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

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

In this commit, global actions where exported in
ActionTemplateItem/erp5/portal_actions/action_id and not in
ActionTemplateItem/portal_types/portal_actions/action_id anymore. This change
restores the previous behaviour.



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

don't create an user preference if this script is called by anonymous (typical use case: web site registration)

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

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

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