Selection.getParams method), so cast the value to a dict.


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

when we call build with activate_kw


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

unrestrictedTraverse is no suitable for this use: it can raise another exception than KeyError (see OFS/Traversable.py) and also prevents from finding methods on object (only subobjects or objects accessible via acquisition context).


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

* Handle HTTP_ACCEPT_LANGUAGE better.

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

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

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

Do not try to translate Next&Previous button labels at client side. Translation is provided from server.

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

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

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

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

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

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

In some cases (including our unit test environments), these ZSQL methods return wrong value if user-defined variables are initialised with empty string, but they return correct value if initialised with NULL instead.


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

Fixed Planning box. The domain generator scripts adds float to the dates to get the next day, but this will not always get to the next day.

This domains scripts will be refatored to use DateUtils.py.

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

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

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

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

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

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

 - Move try..finaly block in Message.__call__ to contain all code executed after security context is changed.
 - Raise an error in Message.__call__ when method is not found.
 - Raise a dummy exception in Message.setExecutionState when there is no previous exception nor any given exception. This allows handling both cases in a single way.


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

Add a test for error paths: error data must be present on the message itself. There are 2 (4, actualy) error paths not covered, since they rely on code present in queues (commit after activity execution), and it's not possible to extract message object after error was processed, so it cannot be unit tested. Message commit must be moved to Message.__call__ and ActivityTool.invokeGroup for those cases to be testable.


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

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

Fix case where there is no exception: error_log.raising raises given exc_info if it's a tuple, to make it latest exception and let python logging module get it by itself. But this attemp causes another error if excpetion is None (!), which in turn hides original exception...


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

Stack dump is different if caused by an exception or by a simple dump, so use different formating methods for each one.
Reorder to first log exception before attemping to format it since it might fail: it happens for example when there is an unicode char in exception value and was the reason for commit 22857.


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

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

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

Reindex portal_activities in ERP5Site_reindexAll, since it contains indexed objects: active processes.

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

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

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

* Update xml format.

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

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

Make the setter output log and push entries in Zope's error_log.
Make the setter grab current traceback if no error was found (neither given by parameter nor found via sys.exc_info) to help identifying causes of activity non-execution.


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

split assert statement in two statements


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

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

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

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

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

'' is false so validator.show_warnings and '' is always false and display always that warnings are not displayed. Now it works correctly.


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

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

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