75c6a5dcc1
find -name "*.py" -exec pyupgrade --py3-only --py37-plus {} +
2022-05-01 23:14:41 +02:00
34b758f2bd
black
2022-05-01 23:14:09 +02:00
814af8d837
Various flake8 fixes.
...
- Removed tabs.
- Fixed E731 do not assign a lambda expression, use a def.
- avoid hasattr
2016-06-12 06:51:35 +02:00
cb1bf28c16
Cleanup
...
Follow https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst
to clean up the code.
2016-02-05 09:43:42 +01:00
0713bcd8bc
Use plone i18n domain
...
plone.app.discussion is an official Plone core package,
thus their translations belong to plone.app.locales.
This commit removes the plone.app.discussion domain and changes it for
plone.
This fixes:
https://github.com/plone/plone.app.discussion/issues/66
2015-11-05 00:30:42 +01:00
9066183ea9
2 lines between top level functions/classes
2015-05-03 08:24:08 +02:00
42d12200a7
Don't use session at all for content rules, set the event in the request to be able to access comment attributes. This fixes 'InvalidObjectReference: A new object is reachable from multiple databases.' if comment contains a RichTextValue which contains a RawValueHolder (persistent object).
2014-09-20 14:54:02 +02:00
13830715a7
Add custom content rules string substitutions
...
- Add content rules string substitutions for comment:
- id
- text
- author email
- author user name
- author full name
2014-04-18 16:36:06 +03:00
ab926d6a10
Update change log
...
Conflicts:
CHANGES.rst
2014-04-18 16:35:45 +03:00
14d4382ca6
Use commented object as context instead of comment within event trigger
...
- In order this to work with plone.contentrules use commented object as
the main context within custom discussion events and add comment as the
second parameter.
2014-04-18 16:33:12 +03:00
4343197209
Trigger custom comment events on comment add/remove/reply
...
Conflicts:
plone/app/discussion/interfaces.py
2014-04-18 16:32:43 +03:00
Jens W. Klein
Maurits van Rees
Gil Forcada
Vincent Fretin
Alin Voinea