a blog will receive notifications only for published posts. They
will not receive all comments of all posts anymore.
When commenting a post users will receive the answers.
Added tests to try to test this behavior.
A squashed merge is required as the conversion of the apiculture branch from
bzr to git was not correctly done. The git history contains irrelevant blobs
and commits. This branch brings a lot of changes and fixes, too many to list
exhaustively.
- New orm api, objects are now used instead of ids
- Environements to encapsulates cr uid context while maintaining backward compatibility
- Field compute attribute is a new object oriented way to define function fields
- Shared browse record cache
- New onchange protocol
- Optional copy flag on fields
- Documentation update
- Dead code cleanup
- Lots of fixes
is now done server-side and stored directly in the html content, as post processing.
The front-end attaches messages based on the attribute data-chatter-id, but do not
compute the attribute itself anymore.
Misc cleaning of code.
bzr revid: tde@openerp.com-20140403112656-ane3ovhh70qdc8b4
display partner-related stuff without having to tweak the access rights.
Misc update of templates due to some filed renaming.
Added author field on the blog, allowing to avoid having issues with
create_uid field.
bzr revid: tde@openerp.com-20140402140200-a3g0750akro2n12v
- default value for post name and subtitle, because using it through the front-end
is the only way it shoudl be used, and the behavior should always be consistent
- moved mail_message new field into its own mail_message.py file to ease the
module reading;
- renamed discussion into discussion_key, a bit more understandable
- link cleaning
bzr revid: tde@openerp.com-20140402111656-0h66yedwm36m6c7t
- removed template field from category. This field was coming from the old document_page module. However
it has been decided to not keep the template feature on categories. Previously there was an onchange
in the document_page form view, allowign to define a template on the page category that will be a default
value for the page content. It has been decided to drop that feature because of the complexity to manage
snippets / html in the category without adding a category editor in the website front-end.
- updated data/demo/views accordingly
- to replace the template feature, it will be possible to duplicate a blog post directly in the front-end.
This will come in a future patch. However the copy method of blog_post has already been fixed to avoid
duplicating website_message_ids, and to reset website_published (_datetime) fields.
bzr revid: tde@openerp.com-20131011125832-dou1ep9ey2ffwa7s
we would like to impose in OpenERP addons :
- model-related files: in models directory
- data/demo files: in data directory
- renamed sexurity/website_mail.xml to website_blog.xml, to avoid confusing the module with website_mail
bzr revid: tde@openerp.com-20131011081215-jnsyqyk7zzrw22qg