IOW, be nice with the OS and other software/users.

- /tmp should never be hardcoded: $TMPDIR is better
- $TMPDIR should be only used with 'tempfile' and appropriate clean up
- in unit tests, the 'tests' directory can be used as temporary storage
  (like in this commit)

This fixes possible random failures of SyncML related tests when, for example,
testERP5SyncML and testERP5DocumentSyncML are run in parallel.

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

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

 - updated change log

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

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

backport SimulationMovement.asComposedDocument() and modify TradeCondition.getTradeModelLineComposedList() so as to search trade model lines from the nearest delivery in the simulation tree.


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

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

allow specialise category in line level, and allow acquisition from parent in order type and delivery type for specialise base category.


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

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

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

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

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

At most 1 message for a given serialization tag can be validated (cf [28706]).
Respect priority/date/uid when validating only 1 message (cf [34632]).

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

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

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

constraints messages without .


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

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

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

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

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

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

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

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

defined in preferences those properties are taken into account when the user
views an image.


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

set a title on this interaction workflow as Transformation already have a workflow named Interaction Workflow Definition that make confusing in the jump menu.

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

change the bad security on the methods, thanks you Jerome.


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

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

  -If an exception is raised when sending mail, the error is not lost
   (available in zope event.log)
  -If an exception is raised when using the site error logger, the error is not
   lost. This test passes for SQLDict, but fails if activity is SQLQueue
  -If a traceback could not be generated, a mail can still be sent


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

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

cache without overwrite previous conversion when processed at the same time.
This test show that conversion cache design is not scallable.

All conversions are stored in a unique dictionary per Document.
This dictionary can not be modified by parallel threads because 
multiple copies of this dictionary are distributed among threads.
When The last thread finish, it take precedence and erase previous
copies of that dictionary.



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

in testDms bootstrap step.


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

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

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

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

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

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

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

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

Using id change a bit the behaviour and can bring new small ambiguities :
- If the web developer create manually a fieldset containing one of the class ('right', 'left'), the javascript will try to create the table containing the fieldset
- if the web developer create a fieldset with name 'center_left' and an extra class 'right'  (using parenthesis in the group name), the javascript will position the fieldset on the right side.
This cases should be very rare (second one is like a mistake). This problem could be avoided by changing template and css to not use javasacript to position elements (I think that this could be made using pure HTML + CSS).

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

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

* Fix list view forms for sale/purchase invoice module.
* Fix purchase invoice default view action. View form for purchase invoice transaction was used.
* Remove detail action from purchase invoice portal type. It was not an action for purchase invoice.

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