[FIX] resource: update default calendar timezone on first admin login #84258
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
kbapt
reviewed
Feb 18, 2022
When the admin user logs in for the first time, their timezone can be updated based on the cookies of their browser. In such case, the timezone of the default working calendar should be updated too. Related: odoo#83262 Task 2759592
MissingNoShiny
force-pushed
the
15.0-resource-calendar-tz-admin-login-vila
branch
from
cbd822e
to
895e6bf
Compare
|
@robodoo r+ |
deneuvillem
added a commit
to odoo-dev/odoo
that referenced
this pull request
Mar 13, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: odoo#84258 task-3793313
robodoo
pushed a commit
that referenced
this pull request
Apr 18, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: #84258 task-3793313 closes #157583 Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
fw-bot
pushed a commit
to odoo-dev/odoo
that referenced
this pull request
Apr 18, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: odoo#84258 task-3793313 X-original-commit: b280a9b
fw-bot
pushed a commit
to odoo-dev/odoo
that referenced
this pull request
Apr 18, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: odoo#84258 task-3793313 X-original-commit: b280a9b
fw-bot
pushed a commit
to odoo-dev/odoo
that referenced
this pull request
Apr 18, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: odoo#84258 task-3793313 X-original-commit: b280a9b
fw-bot
pushed a commit
to odoo-dev/odoo
that referenced
this pull request
Apr 18, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: odoo#84258 task-3793313 X-original-commit: b280a9b
fw-bot
pushed a commit
to odoo-dev/odoo
that referenced
this pull request
Apr 18, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: odoo#84258 task-3793313 X-original-commit: b280a9b
fw-bot
pushed a commit
to odoo-dev/odoo
that referenced
this pull request
Apr 19, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: odoo#84258 task-3793313 X-original-commit: b280a9b
fw-bot
pushed a commit
to odoo-dev/odoo
that referenced
this pull request
Apr 19, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: odoo#84258 task-3793313 X-original-commit: b280a9b
robodoo
pushed a commit
that referenced
this pull request
Apr 22, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: #84258 task-3793313 closes #162498 X-original-commit: b280a9b Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Apr 22, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: #84258 task-3793313 closes #162471 X-original-commit: b280a9b Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Apr 22, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: #84258 task-3793313 closes #162541 X-original-commit: b280a9b Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Apr 22, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: #84258 task-3793313 closes #162571 X-original-commit: b280a9b Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Apr 22, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: #84258 task-3793313 closes #162561 X-original-commit: b280a9b Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Apr 22, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: #84258 task-3793313 closes #162518 X-original-commit: b280a9b Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Apr 22, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: #84258 task-3793313 closes #162531 X-original-commit: b280a9b Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
willylohws
pushed a commit
to willylohws/odoo
that referenced
this pull request
May 1, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: odoo#84258 task-3793313 closes odoo#162531 X-original-commit: b280a9b Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
willylohws
pushed a commit
to willylohws/odoo
that referenced
this pull request
May 1, 2024
… (follow-up) Steps to reproduce: ------------------- 1. Install the resource module without demo data (or install any module which depends on it, again without demo data). 2. Login with the administrator user for the first time. 3. The default resource calendar (e.g. "Standard 40 hours/week") timezone will be set to 'UTC' by default while it should be set to the timezone of the administrator. Fix: ------------------- When there is no demo data, no resource_calendar_id is linked to the admin. In this case, we need to retrieve the record of the default working calendar and set its timezone to the one of the admin user on the first login. This is a follow-up of this fix: odoo#84258 task-3793313 closes odoo#157583 Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
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.
When the admin user logs in for the first time, their timezone can be updated based on the cookies of their browser.
In such case, the timezone of the default working calendar should be updated too.
Related: #83262
Task 2759592