[FIX] portal: fix frontend chatter move

Commit 3cfd64f63f moved the frontend chatter from a website-based module
website_mail to portal. Purpose was to allow its use in customer
portal independently from the website.

However some renaming done during the move was not properly propagated
resulting in the chatter not being loaded. This commit fixes that by
correctly using the new class node as well as widget name when
instantiating the widget.
This commit is contained in:
Thibault Delavallée
2017-08-25 15:24:35 +02:00
parent 349b5d724f
commit 8f93369d83
2 changed files with 6 additions and 3 deletions
+4 -1
View File
@@ -15,11 +15,14 @@ portal.
This module contains most code coming from odoo v10 website_portal. Purpose
of this module is to allow the display of a customer portal without having
a dependency towards website edition and customization capabilities.""",
'depends': ['http_routing', 'mail'],
'data': [
'data/portal_data.xml',
'views/assets.xml',
'views/portal_templates.xml',
'wizard/portal_wizard_views.xml',
],
'depends': ['http_routing', 'mail'],
'qweb': [
'static/src/xml/portal_chatter.xml',
],
}
@@ -224,9 +224,9 @@ var PortalChatter = Widget.extend({
});
base.ready().then(function () {
$('.o_website_mail_thread').each(function (index) {
$('.o_portal_chatter').each(function (index) {
var $elem = $(this);
var mail_thread = new WebsiteMailThread(null, $elem.data());
var mail_thread = new PortalChatter(null, $elem.data());
mail_thread.appendTo($elem);
});
});