Skip to content
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

User is unable to lock content because of validation limit on locked_by column of contentlet_version_info #24133

Closed
muhammadfaizandotcms opened this issue Feb 16, 2023 · 1 comment · Fixed by #24758
Assignees

Comments

@muhammadfaizandotcms
Copy link

muhammadfaizandotcms commented Feb 16, 2023

Problem Statement

Needs to increase character length limit of locked_by column of contentlet_version_info.
If the user id character length from the user_ table is greater than 36 then the user is unable to lock the content.
Relevant Ticket: https://dotcms.zendesk.com/agent/tickets/110022.

Steps to Reproduce

  1. login to the demo site
  2. create a new user and give appropriate permissions to create or edit the content.
  3. Change the user-id from the user__ table in the database and set the length greater than 36.
  4. Now login with newly created user credentials and try to lock the content.
  5. See the toast error on the screen.

Acceptance Criteria

Customers coming from pretty old versions go through this UT Task00795LiveWorkingToIdentifier which creates tables with 36 lengths.

We need a UT which updates the locked_by to 100 for the following tables, just for Postgres:

  • contentlet_version_info
  • container_version_info
  • template_version_info
  • link_version_info

dotCMS Version

22.03.4

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

ERROR: value too long for type character varying(36){
  "SQL": ["UPDATE contentlet_version_info SET working_inode=?, live_inode=?, deleted=?, locked_by=?, locked_on=?, version_ts=? WHERE identifier=? AND lang=?"],
  "maxRows": [-1],
  "offest": [0],
  "params": [
    "86d192d9-e480-437e-a44b-c513a7e8f14d",
    "86d192d9-e480-437e-a44b-c513a7e8f14d",
    false,
    "5b3b6246b6b69ad75d8f4a33492299d0ba4440b4e9f38b54588b5984738ac894",
    "2023-02-13 08:14:14.162",
    "2023-02-10 09:24:08.237",
    "61ac84bc-fd71-432f-90a0-5d3565e516c6",
    1
  ]
}

Sub-Tasks & Estimates

No response

@AndreyDotcms AndreyDotcms linked a pull request Apr 26, 2023 that will close this issue
3 tasks
erickgonzalez pushed a commit that referenced this issue Apr 27, 2023
* #24133 Creating new task to alter the lenght, changing the base branch of the issue

* #24133 Fixing the way that the created test and task are been called
@erickgonzalez erickgonzalez reopened this Apr 27, 2023
@bryanboza
Copy link
Member

Fixed, unable to reproduce on release-23.06 // Docker // FF

@erickgonzalez erickgonzalez added the Release : 23.01.4 Included in LTS patch release 23.01.4 label Jun 7, 2023
erickgonzalez added a commit that referenced this issue Jun 14, 2023
@erickgonzalez erickgonzalez added the Release : 22.03.7 Included in LTS patch release 22.03.7 label Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

6 participants