NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[IMP] marketing: match the Display Timezone description with tooltips

Browse Source 
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
This commit is contained in:
lase@odoo.com 2024-12-17 14:27:04 +01:00 committed by Zachary Straub (ZST)
parent 5a19d0c718
commit e8793e166c
1 changed files with 13 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
content/applications/marketing/events/event_essentials.rst
View File

@ -43,8 +43,10 @@ Odoo database or by creating and editing new field data. Key information to ente
includes: includes:
- :guilabel:`Event Name`: give the event a title. - :guilabel:`Event Name`: give the event a title.
- :guilabel:`Date`: includes the start and end dates/times for the event. - :guilabel:`Date`: when the event is scheduled to take place (expressed in your local timezone on
- :guilabel:`Timezone`: covers the timezone for when the event is taking place. the form view).
- :guilabel:`Display Timezone`: indicates the timezone in which the event dates/times will be
displayed on the website.
- :guilabel:`Template`: choose from a pre-built event template or build a custom one and connect it - :guilabel:`Template`: choose from a pre-built event template or build a custom one and connect it
here. here.
- :guilabel:`Tags`: add tags to indicate briefly what the event is for (e.g. `tradeshow`). Tags - :guilabel:`Tags`: add tags to indicate briefly what the event is for (e.g. `tradeshow`). Tags
@ -84,8 +86,8 @@ Send automated emails, text, and social posts to event attendees
Under the :guilabel:`Communication` tab, configure personalized email, SMS, or social post messages Under the :guilabel:`Communication` tab, configure personalized email, SMS, or social post messages
to keep in touch with event attendees. For each communication, click :guilabel:`Add a line` in the to keep in touch with event attendees. For each communication, click :guilabel:`Add a line` in the
:guilabel:`Communication` tab form, and then choose (or create) a communications template using :guilabel:`Communication` tab form, and then choose (or create) a communications template using the
the drop-down menu under the :guilabel:`Template` column. drop-down menu under the :guilabel:`Template` column.
Next, define the :guilabel:`Interval` and :guilabel:`Unit` of time for how often the communication Next, define the :guilabel:`Interval` and :guilabel:`Unit` of time for how often the communication
should be sent; use these time fields to specify the frequency of :guilabel:`Hours`, should be sent; use these time fields to specify the frequency of :guilabel:`Hours`,
@ -112,8 +114,8 @@ To create a questionnaire, from the :guilabel:`Events` application, navigate to
:menuselection:`Configuration --> Settings` and then enable the :guilabel:`Questions` setting. :menuselection:`Configuration --> Settings` and then enable the :guilabel:`Questions` setting.
With the setting enabled, questions and answers can now be added (and recorded) under the the With the setting enabled, questions and answers can now be added (and recorded) under the the
:guilabel:`Questions` tab back on the event form. For each question, specify if it should only :guilabel:`Questions` tab back on the event form. For each question, specify if it should only be
be asked once with the :guilabel:`Ask once per order` checkbox, or if the question requires a asked once with the :guilabel:`Ask once per order` checkbox, or if the question requires a
:guilabel:`Mandatory Answer`, which will make the question required for registration. :guilabel:`Mandatory Answer`, which will make the question required for registration.
.. example:: .. example::
@ -267,12 +269,12 @@ Publish events
Until an event is published, it will remain hidden from public view on the website and registering Until an event is published, it will remain hidden from public view on the website and registering
for it will not be possible. To publish an event, navigate to it either from the backend of Odoo for it will not be possible. To publish an event, navigate to it either from the backend of Odoo
through the :guilabel:`Events` application, or access the hidden event page through the frontend through the :guilabel:`Events` application, or access the hidden event page through the frontend as
as either a priveliged user or administrator. either a priveliged user or administrator.
If navigating from the backend, go to the event form, and click the :guilabel:`Go to Website` If navigating from the backend, go to the event form, and click the :guilabel:`Go to Website` smart
smart button to reach the event page on the website (on the frontend). If starting from the frontend button to reach the event page on the website (on the frontend). If starting from the frontend,
, simply navigate to the event page that needs to be published. simply navigate to the event page that needs to be published.
No matter the route, an event page can only be published from the frontend. In the upper right No matter the route, an event page can only be published from the frontend. In the upper right
corner of the event page on the website, toggle the switch from the red :guilabel:`Unpublished` corner of the event page on the website, toggle the switch from the red :guilabel:`Unpublished`