Odoo Changelog — 2020-06-24

Wednesday, June 24, 2020

3 changes · master

Bug Fixes(3)

Resolved issues and error corrections

[FIX] doc: meta directive support

Coremasterdoc

This fixes documentation page handling so custom metadata, such as SEO descriptions or keywords, can be added correctly per page. It helps improve search visibility and removes duplicated template logic, with no expected impact on regular Odoo users.

Original PR description

The translator defined a `meta` attribute, however: * it was static so couldn't be expanded using the `meta` directive, move to instance attribute, and create an `add_meta` method which adds some…

The translator defined a `meta` attribute, however:

* it was static so couldn't be expanded using the `meta` directive,
  move to instance attribute, and create an `add_meta` method which
  adds some indentation (for a cleaner HTML output)
* the `meta` directive itself was not supported by the translator
* turns out HTMLWriter just removes the first to entries of `meta` as
  "cleanup", which explains why we had to duplicate it in the template
  - therefore pad the `meta` list and remove entries from template
  - move front to linktags, that seems more relevant

@mart-e seems like it'd be useful for task 2121586 (doc SEO) as then SEO meta tags could be added on a per-document basis [using the meta directive](https://docs.readthedocs.io/en/latest/guides/technical-docs-seo-guide.html#use-meta-tags), though it would also need to be ported to the user documentation.

Maybe it's time to work on the Great Unification between the user and technical docs somehow? Not quite sure whether we want to handle this by moving our custom extensions to pypi or submodules or subtrees or something. We'd probably still need to sync both docs to the "doc extensions repository" but it would likely be easier than needing to remember to copy updates from one to the other.

#documentation#SEO#metadata

[FIX] mass_mailing : remove space between alerts

PR #53291

Coremastermass_mailing

This fixes an unwanted gap between alert messages in the mass mailing screen. The change makes scheduled or in-progress mailing alerts look cleaner and easier to read.

Original PR description

Before this commit there is space between alerts. It's not pretty.
It only occur when a mailing is scheduled and mail have already be send (or un
progress)

task-2275560

#mailing#alerts#interface

[FIX] web_grid: prevent traceback when grouping

PR #11254

Enterprisemasterweb_grid

Users can now group grid views by multiple fields without triggering an error if the first grouping is still loading. This improves reliability when analyzing data in grid views and prevents interruptions during reporting workflows.

Original PR description

Before this commit, when the user grouped by multiple fields before the
first group by was done, they were getting a traceback.

TaskID: 2279400

#grid view#grouping#stability

The translator defined a `meta` attribute, however: * it was static so couldn't be expanded using the `meta` directive, move to instance attribute, and create an `add_meta` method which adds some indentation (for a cleaner HTML output) * the `meta` directive itself was not supported by the translator * turns out HTMLWriter just removes the first to entries of `meta` as "cleanup", which explains why we had to duplicate it in the template - therefore pad the `meta` list and remove entries from template - move front to linktags, that seems more relevant @mart-e seems like it'd be useful for task 2121586 (doc SEO) as then SEO meta tags could be added on a per-document basis [using the meta directive](https://docs.readthedocs.io/en/latest/guides/technical-docs-seo-guide.html#use-meta-tags), though it would also need to be ported to the user documentation. Maybe it's time to work on the Great Unification between the user and technical docs somehow? Not quite sure whether we want to handle this by moving our custom extensions to pypi or submodules or subtrees or something. We'd probably still need to sync both docs to the "doc extensions repository" but it would likely be easier than needing to remember to copy updates from one to the other.