An error occurred fetching the project authors.
- 21 Oct, 2011 12 commits
-
-
Łukasz Nowak authored
Really never raise (trust no one). Always return excepted values in order to not trick caller.
-
Łukasz Nowak authored
-
Kazuhiko Shiozaki authored
-
Łukasz Nowak authored
Non transmitted values shall result in ++ Empty (evaluated to None) values shall result in ++
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
create a dedicated folder for xinha to avoid conflict of images folder. fix script tag usage to load external javascripts.
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Caller might try to log the transmission XMLs and raising would result in aborted transaction.
-
Łukasz Nowak authored
-
Łukasz Nowak authored
-
Kazuhiko Shiozaki authored
otherwise imagemagick will create black-background image when resizing. http://studio.imagemagick.org/discourse-server/viewtopic.php?f=3&t=19677
-
- 20 Oct, 2011 4 commits
-
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Guillaume Bottex authored
-
Guillaume Bottex authored
-
- 19 Oct, 2011 9 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
In case of failure, reserved messages were freed before finalization. This was useless because finalization frees them and dangerous because another zope could start processing a message that should not be executed again.
-
Julien Muchembled authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Ivan Tyagov authored
In other parts of ERP5 we do not specify it. As image resolution should be handled as a system preference (as other image properties like quality, format, etc..) do not specify it any more in generated UI image links. Just let system use provided defaults.
-
Aurel authored
-
Nicolas Delaby authored
- Remove acquired permissions
-
Ivan Tyagov authored
If pre_converted_only is True system will return desired conversion only if it's already cached. Extend testDms to cover it.
-
- 18 Oct, 2011 3 commits
-
-
Vincent Pelletier authored
Allows FormBox to contain fields outside "left" group. The use of this is most evident when FormBox is in the "bottom" group: it allows included form to have field groups with borders (left, right, center) or without borders (bottom), hence allowing competely extending base form. This required rewriting JS code stitching "left" & "right" groups together so it honours nesting. For backward compatibility, hide "left" groups rendered inside any bordered group - but only when there is no field in "right" group. Also, clean up duplicated code in embedded_form_render and use proper naming (templates used by forms should always end with "_view").
-
Leonardo Rochael Almeida authored
-
Yusei Tahara authored
-
- 17 Oct, 2011 7 commits
-
-
Julien Muchembled authored
-
Leonardo Rochael Almeida authored
And add a test checking this in portal_rules
-
Leonardo Rochael Almeida authored
-
Julien Muchembled authored
-
Julien Muchembled authored
- PEP 308: Conditional Expressions - PEP 341: Unified try/except/finally - PEP 343: The ‘with’ statement
-
Julien Muchembled authored
Checked following occurrences in comments: - "Python 2.[456]" - "Zope 2.[891]" - "BBB" - "BACK" Checked uses of: - email, hashlib, numpy & tarfile (modules) - ImportError - string.Template - suppress_events (parameter of _setObject) Excluded: - some forked modules (MailTemplates, PortalTransforms...) - some i18n compatibility code
-
Aurel authored
-
- 14 Oct, 2011 5 commits
-
-
Aurel authored
-
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-