-
Notifications
You must be signed in to change notification settings - Fork 469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent 404 issues for customers who came from another DB engine #30243
Labels
OKR : Customer Success
Owned by Arno
OKR : Customer Support
Owned by Scott
Priority : 1 Show Stopper
QA : Approved
Release : 23.10.24 v18
Included in LTS patch release 23.10.24 v18
Release : 24.04.24 v10
Included in LTS patch release 24.04.24 v10
Release : 24.11.11
Team : Bug Fixers
Type : Defect
Comments
erickgonzalez
added a commit
that referenced
this issue
Oct 3, 2024
erickgonzalez
added a commit
that referenced
this issue
Oct 4, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 8, 2024
During the migration of customers from another database engine to Postgres, a column was inadvertently left behind. This oversight has resulted in 404 errors because in Postgres, the column is interpreted as a function, not a column. Added a note in the MainSuite2a since it lasts twice than other suites.
erickgonzalez
added a commit
that referenced
this issue
Oct 23, 2024
erickgonzalez
added a commit
that referenced
this issue
Oct 23, 2024
Fixed, unable to reproduce using the provided steps, now I'm able to open the file without problems |
spbolton
pushed a commit
that referenced
this issue
Nov 11, 2024
During the migration of customers from another database engine to Postgres, a column was inadvertently left behind. This oversight has resulted in 404 errors because in Postgres, the column is interpreted as a function, not a column. Added a note in the MainSuite2a since it lasts twice than other suites.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
OKR : Customer Success
Owned by Arno
OKR : Customer Support
Owned by Scott
Priority : 1 Show Stopper
QA : Approved
Release : 23.10.24 v18
Included in LTS patch release 23.10.24 v18
Release : 24.04.24 v10
Included in LTS patch release 24.04.24 v10
Release : 24.11.11
Team : Bug Fixers
Type : Defect
Parent Issue
#30000
Problem Statement
After getting the new logs, saw that the 404 was coming from the Identifier:
The code we use to get the identifier is the following:
core/dotCMS/src/main/java/com/dotmarketing/business/IdentifierFactoryImpl.java
Lines 145 to 176 in 5a7e977
Looking at the code, this column full_path_lc should be a function, not a column (at least in Postgres); for customers that were migrated from another DB engine, this was kept as a column and wasn't being filled.
Steps to Reproduce
Only Reproducible with customer data.Acceptance Criteria
Pages and Files should return 200.
Create a UT that does the following:
1- Remove full_path_lc column:
2- Create the function if it doesn’t exists:
3- Create index (first check if exists):
dotCMS Version
22.03 LTS and 24.04 LTS.
Proposed Objective
Customer Success
Proposed Priority
Priority 1 - Show Stopper
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
https://helpdesk.dotcms.com/a/tickets/27067
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: