Monday, April 19, 2021
3 changes · master
Enhancements to existing features
Updates the new-user welcome wording so it no longer assumes a user's gender. This makes the sign-up experience more inclusive and improves the quality of the default English text.
Original PR description
Description of the issue/feature this PR addresses: As discussed and suggested by @mart-e in issue #67124. Current behavior before PR: Assumption that all new users arriving in Odoo can be addressed as "him" and "his" Desired behavior after PR is merged: The new text is gender neutral and appropriate English grammar. I'm new at this, but I've done my best to follow the guidelines. As requested by @mart-e I am creating this PR against master. The same male-oriented phrase exists in English in translation files such as: - auth_signup/i18n/az.po - auth_signup/i18n/gu.po - and others I don't know the process to suggest the same update to those. Help from another member would be appreciated. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website theme selection view now uses improved theme descriptions, making it easier for users to understand and compare available themes. This helps business users choose a suitable website look with less guesswork.
Original PR description
Task : https://tinyurl.com/8jse3wn2 This PR is linked to : https://github.com/odoo/design-themes/pull/461 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The event track proposal email template has been cleaned up to remove unnecessary blank areas and avoid repeating the track name in internal chatter messages. This makes event communication clearer for users, with only a minor tradeoff that some reply email subjects may reference the event name instead of the track name.
Original PR description
This commit slightly reworks the "event_track_template_new" template to format it a little better and get rid of unnecessary blank sections. The "subject" param was removed from the "message_post_with_view" call as we don't want the chatter to contain the name of the track twice. Indeed, since #61570, the "subject" is displayed in the chatter if it differs from the thread name (which is the case here). This causes a small regression for emails that will state "Re: EventName" in their subject instead of the track name, but it's deemed acceptable to have a nicer chatter message. We also remove the description of the "mt_event_track" mail.message.subtype as it's only used with a custom template and is redundant with that template's content. Task-2496444