ajung/plone.app.discussion
ajung/plone.app.discussion
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1,754 Commits 1 Branch 0 Tags 5 MiB
19fe254916
Commit Graph

7 Commits

Author SHA1 Message Date
Gil Forcada
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
Gil Forcada
9066183ea9 2 lines between top level functions/classes 2015-05-03 08:24:08 +02:00
Vincent Fretin
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
Alin Voinea
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
Alin Voinea
ab926d6a10 Update change log 
Conflicts:
	CHANGES.rst
 2014-04-18 16:35:45 +03:00
Alin Voinea
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
Alin Voinea
4343197209 Trigger custom comment events on comment add/remove/reply 
Conflicts:
	plone/app/discussion/interfaces.py
 2014-04-18 16:32:43 +03:00