<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Odoo/addons/website_forum/data/forum_data.xml, branch 14.0</title>
<subtitle>The current checkout of upstream Odoo</subtitle>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/'/>
<entry>
<title>[IMP] website_forum: rename fields, labels, texts,...</title>
<updated>2020-05-14T18:27:00+00:00</updated>
<author>
<name>Okan SUMER (osu)</name>
<email>osu@odoo.com</email>
</author>
<published>2020-03-18T15:55:18+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=bfb70b6b9c0afceaa145d5053ea68e1d1e08d21e'/>
<id>bfb70b6b9c0afceaa145d5053ea68e1d1e08d21e</id>
<content type='text'>
This commit rename every "Question" references by "Post"
to make it appropriate for both forum's type (Question and Discussion)
It renames some other fields/labels to be shorter or with a
capital letter at the start.
Update demo data to add a title to answers

Part of https://github.com/odoo/odoo/pull/46634

task-2201708</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This commit rename every "Question" references by "Post"
to make it appropriate for both forum's type (Question and Discussion)
It renames some other fields/labels to be shorter or with a
capital letter at the start.
Update demo data to add a title to answers

Part of https://github.com/odoo/odoo/pull/46634

task-2201708</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] *: use `ref=` instead of `eval="ref('` in xml field tags.</title>
<updated>2020-02-11T13:07:06+00:00</updated>
<author>
<name>Victor Feyens</name>
<email>vfe@odoo.com</email>
</author>
<published>2020-02-07T13:42:17+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=d4e0fe018d05fd0dc3e9ab77977d6e97440c73c0'/>
<id>d4e0fe018d05fd0dc3e9ab77977d6e97440c73c0</id>
<content type='text'>
* Code cleanup
* Avoid a safe evaluation of the field value when loading those records.

closes odoo/odoo#44883

Related: odoo/enterprise#8283
Signed-off-by: Victor Feyens (vfe) &lt;vfe@odoo.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Code cleanup
* Avoid a safe evaluation of the field value when loading those records.

closes odoo/odoo#44883

Related: odoo/enterprise#8283
Signed-off-by: Victor Feyens (vfe) &lt;vfe@odoo.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] website_forum, *: revamp design</title>
<updated>2019-10-01T16:52:20+00:00</updated>
<author>
<name>sri-odoo</name>
<email>sri@odoo.com</email>
</author>
<published>2019-08-29T13:48:12+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=c8c8eb3d5652e9834d0ecd5aad907ee359edb657'/>
<id>c8c8eb3d5652e9834d0ecd5aad907ee359edb657</id>
<content type='text'>
* web_editor, website_profile

Part of https://github.com/odoo/odoo/pull/35749
task-2024197

Co-authored-by: Jérémy Kersten &lt;jke@odoo.com&gt;
Co-authored-by: qsm-odoo &lt;qsm@odoo.com&gt;
Co-authored-by: fja-odoo &lt;fja@odoo.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* web_editor, website_profile

Part of https://github.com/odoo/odoo/pull/35749
task-2024197

Co-authored-by: Jérémy Kersten &lt;jke@odoo.com&gt;
Co-authored-by: qsm-odoo &lt;qsm@odoo.com&gt;
Co-authored-by: fja-odoo &lt;fja@odoo.com&gt;</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] *: put all mail.message.subtype as noupdate</title>
<updated>2019-03-28T13:40:41+00:00</updated>
<author>
<name>Nans Lefebvre</name>
<email>len@odoo.com</email>
</author>
<published>2019-03-04T06:19:19+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=c26eb41f9e1999b8be188471f34bf08a7d4adb96'/>
<id>c26eb41f9e1999b8be188471f34bf08a7d4adb96</id>
<content type='text'>
The mail.message.subtype model contains a field internal,
which decides if the messages are visible to external users or not.
Such a value should not be overriden at module update,
so all subtypes should be in noupdate.

opw 1946043

closes odoo/odoo#32214

Signed-off-by: Nans Lefebvre (len) &lt;len@odoo.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The mail.message.subtype model contains a field internal,
which decides if the messages are visible to external users or not.
Such a value should not be overriden at module update,
so all subtypes should be in noupdate.

opw 1946043

closes odoo/odoo#32214

Signed-off-by: Nans Lefebvre (len) &lt;len@odoo.com&gt;</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] website(_profile,_forum,_slides): move validation email to profile and use in forum and elearning</title>
<updated>2019-03-15T14:58:28+00:00</updated>
<author>
<name>David Beguin</name>
<email>dbe@odoo.com</email>
</author>
<published>2019-02-20T16:54:36+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=fb40c6bf6018f7f208201e1d4a4d413fd2ce3080'/>
<id>fb40c6bf6018f7f208201e1d4a4d413fd2ce3080</id>
<content type='text'>
Email validation was necessary on the forum to be able to begin to use the forum
(ask or answer questions, vote, etc..)

As the new elearning also uses karma since 705376a982d64fb41800f148a167ef0fc28ce4c6,
the email validation is now also necessary in the eLearning platform.

This is why this commit is moving the email validation process to website_profile
and extend website_slides (eLearning) and website_forum to use this feature.

In function of where the user asked to send him the validation email,
the user is redirected on the forum or on the elearning when he clicks on
'Validate my account' in the received 'email validation' email.

Task ID : 1943788
PR #31321</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Email validation was necessary on the forum to be able to begin to use the forum
(ask or answer questions, vote, etc..)

As the new elearning also uses karma since 705376a982d64fb41800f148a167ef0fc28ce4c6,
the email validation is now also necessary in the eLearning platform.

This is why this commit is moving the email validation process to website_profile
and extend website_slides (eLearning) and website_forum to use this feature.

In function of where the user asked to send him the validation email,
the user is redirected on the forum or on the elearning when he clicks on
'Validate my account' in the received 'email validation' email.

Task ID : 1943788
PR #31321</pre>
</div>
</content>
</entry>
<entry>
<title>[MOV] gamification, website_forum : move karma data and demo in gamification</title>
<updated>2019-02-12T11:23:34+00:00</updated>
<author>
<name>David Beguin</name>
<email>dbe@odoo.com</email>
</author>
<published>2019-02-11T13:33:09+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=b0aa6f654b7d8a8796d4a82d87f19727ac9a67b8'/>
<id>b0aa6f654b7d8a8796d4a82d87f19727ac9a67b8</id>
<content type='text'>
As gamification karma-based features can be used outside of forum let us
move demo and data directly in gamification. It will be used notably for
eLearning.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
As gamification karma-based features can be used outside of forum let us
move demo and data directly in gamification. It will be used notably for
eLearning.</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] web_editor, website(_*): fix bs4</title>
<updated>2018-08-31T14:37:45+00:00</updated>
<author>
<name>Romain Derie</name>
<email>rde@odoo.com</email>
</author>
<published>2018-08-27T16:26:55+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=6bfb0810b0cc60ee92d68613cb0e94cf85143d43'/>
<id>6bfb0810b0cc60ee92d68613cb0e94cf85143d43</id>
<content type='text'>
[FIX] web_editor: adapt col size to avoid too small select

We should avoid col-md-3 in col-md-9 as the menu dialog is instanciated at 2
places:
  - When creating a link in the editor
  - When editing website navbar menu

In the second case, there is a hack in `content.js` to remove `modal-lg`
lowering the width of the modal and making the select too small.

[FIX] website: lower navbar font size

With BS4, font-size of navbar element went from 13px to ~17px (rem unit
computation).

14px seems better than previous 13px as the frontend content size is
higher than the backend one. Thus, 13px looks too small in contrast with the
frontend page content.

[FIX] website_crm_partner_assign, website_customer, website_membership: fix layout

This commit fixes multiple layout issues, mainly by aligning code of the 3
modules:
  - Add margin right to avoid text to be against image
  - Using image_medium everywhere
  - Fixing search input width

publish toggle red + odoo primary is weird -&gt; gray
navbar now has a background &amp; float-right not working since flex
-&gt; remove navbar class, use d-flex and ml-auto so the right element will be floating since using all available width

task-1878150
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
[FIX] web_editor: adapt col size to avoid too small select

We should avoid col-md-3 in col-md-9 as the menu dialog is instanciated at 2
places:
  - When creating a link in the editor
  - When editing website navbar menu

In the second case, there is a hack in `content.js` to remove `modal-lg`
lowering the width of the modal and making the select too small.

[FIX] website: lower navbar font size

With BS4, font-size of navbar element went from 13px to ~17px (rem unit
computation).

14px seems better than previous 13px as the frontend content size is
higher than the backend one. Thus, 13px looks too small in contrast with the
frontend page content.

[FIX] website_crm_partner_assign, website_customer, website_membership: fix layout

This commit fixes multiple layout issues, mainly by aligning code of the 3
modules:
  - Add margin right to avoid text to be against image
  - Using image_medium everywhere
  - Fixing search input width

publish toggle red + odoo primary is weird -&gt; gray
navbar now has a background &amp; float-right not working since flex
-&gt; remove navbar class, use d-flex and ml-auto so the right element will be floating since using all available width

task-1878150
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] base: add regular user admin as uid 2</title>
<updated>2018-08-23T19:38:57+00:00</updated>
<author>
<name>Raphael Collet</name>
<email>rco@odoo.com</email>
</author>
<published>2018-07-23T08:47:19+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=2f7c03d9ca5809b65dc6eaa778064668d34fcd2e'/>
<id>2f7c03d9ca5809b65dc6eaa778064668d34fcd2e</id>
<content type='text'>
User 1 simply becomes a technical user (inactive, no password).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
User 1 simply becomes a technical user (inactive, no password).
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] base: improve kanban of modules, cards not clickable (top-right menu)</title>
<updated>2018-08-05T22:29:51+00:00</updated>
<author>
<name>Fabien Pinckaers</name>
<email>fp@openerp.com</email>
</author>
<published>2018-08-05T20:31:32+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=7c8ab8a574cdef9f8fe3c2df3b2b56e9a03ef79b'/>
<id>7c8ab8a574cdef9f8fe3c2df3b2b56e9a03ef79b</id>
<content type='text'>
[NEW] base: show enterprise module, with an 'upgrade' button
[IMP] *: some modules renaming, and improved copywriting of manifest
[IMP] *: utm on links to odoo.com
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
[NEW] base: show enterprise module, with an 'upgrade' button
[IMP] *: some modules renaming, and improved copywriting of manifest
[IMP] *: utm on links to odoo.com
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] website_forum: make templates more modern and updated with Odoo guidelines</title>
<updated>2018-07-24T13:33:22+00:00</updated>
<author>
<name>Haresh Kansara</name>
<email>hak@odoo.com</email>
</author>
<published>2018-07-20T14:06:21+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=9c31f3d8de4a0334148ad15e0bc2794f4de15dfb'/>
<id>9c31f3d8de4a0334148ad15e0bc2794f4de15dfb</id>
<content type='text'>
In this commit we improve templates used in website_forum. Purpose of this
commit is to have templates that embed or use standard Odoo email layouts to
make them look modern and have a common style across all emails.

Main guidelines

 * better use of div / p / br to try to lessen layout issues, especially
   when updating templates using the editor;
 * correctly sequence the templates fields definition;
 * correctly set templates values notably auto_delete and user_signature
   fields to avoid confusion;
 * correctly layout the email content using light notification email. It
   can either propagate the layout choice through various send mail methods
   or directly embed the styling in the templates for more technical or
   complex templates;
 * use email_formatted computed field when possible to avoid having hand-made
   from / to addresses;
 * fix various typos and improve subjects when necessary;

Content of emails is not necessarily updated as the purpose of this task is
about styling, not content itself.

This commit is linked to task ID 1843224 (and 1868112) and to PR #25313
(and #25889).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In this commit we improve templates used in website_forum. Purpose of this
commit is to have templates that embed or use standard Odoo email layouts to
make them look modern and have a common style across all emails.

Main guidelines

 * better use of div / p / br to try to lessen layout issues, especially
   when updating templates using the editor;
 * correctly sequence the templates fields definition;
 * correctly set templates values notably auto_delete and user_signature
   fields to avoid confusion;
 * correctly layout the email content using light notification email. It
   can either propagate the layout choice through various send mail methods
   or directly embed the styling in the templates for more technical or
   complex templates;
 * use email_formatted computed field when possible to avoid having hand-made
   from / to addresses;
 * fix various typos and improve subjects when necessary;

Content of emails is not necessarily updated as the purpose of this task is
about styling, not content itself.

This commit is linked to task ID 1843224 (and 1868112) and to PR #25313
(and #25889).
</pre>
</div>
</content>
</entry>
</feed>
