[FW][IMP] marketing: match the Display Timezone description with tooltips #11790
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change clarifies the situation according to the update done in the community PR opw-4323142 X-original-commit: fe9d186
|
|
|
This PR targets 18.0 and is part of the forward-port chain. Further PRs will be created up to master. More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port |
|
@lase-odoo this forward port of #11596 is awaiting action (not merged or closed). |
1 similar comment
|
@lase-odoo this forward port of #11596 is awaiting action (not merged or closed). |
robodoo
pushed a commit
to odoo/odoo
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change tries to clarify the situation. opw-4323142 closes #194354 X-original-commit: 88813db Related: odoo/documentation#11790 Signed-off-by: Lancelot Semal (lase) <[email protected]> Signed-off-by: Jérémy Hennecart (jeh) <[email protected]>
robodoo
pushed a commit
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change clarifies the situation according to the update done in the community PR opw-4323142 closes #11790 X-original-commit: fe9d186 Related: odoo/odoo#194354 Signed-off-by: Lancelot Semal (lase) <[email protected]>
robodoo
pushed a commit
to odoo/odoo
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change tries to clarify the situation. opw-4323142 closes #194354 X-original-commit: 88813db Related: odoo/documentation#11790 Signed-off-by: Lancelot Semal (lase) <[email protected]> Signed-off-by: Jérémy Hennecart (jeh) <[email protected]>
robodoo
pushed a commit
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change clarifies the situation according to the update done in the community PR opw-4323142 closes #11790 X-original-commit: fe9d186 Related: odoo/odoo#194354 Signed-off-by: Lancelot Semal (lase) <[email protected]>
robodoo
pushed a commit
to odoo/odoo
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change tries to clarify the situation. opw-4323142 closes #194354 X-original-commit: 88813db Related: odoo/documentation#11790 Signed-off-by: Lancelot Semal (lase) <[email protected]> Signed-off-by: Jérémy Hennecart (jeh) <[email protected]>
robodoo
pushed a commit
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change clarifies the situation according to the update done in the community PR opw-4323142 closes #11790 X-original-commit: fe9d186 Related: odoo/odoo#194354 Signed-off-by: Lancelot Semal (lase) <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
The current descriptions and naming of the
Datefields (date_begin,date_end) and theTimezonefield (date_tz) can be confusing in the form view of the event model. Specifically:The timezone used for converting the form dates to the database is determined by the context and not by the
Timezonefield present on the form. However, thisTimezonefield determines the timezone used for displaying the event's date/time on the website. This change clarifies the situation according to the update done in the community PRopw-4323142
Forward-Port-Of: #11749
Forward-Port-Of: #11596