When the 'uniquePerSite' is set recalculate unique_fields key values

[freddyDOTCMS]

Parent Issue

29459

User Story

If in a unique fields the uniquePerSite field variable is changed then be need recalculated the unique_key hash values for the unique_table, to include or exclude the host id according to the new value.

We need to create a API/Factory methods to do this.

Acceptance Criteria

• Recalculate all the hash after the uniquePerSite field variable is changed

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

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

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

Steps to Reproduce:

• Start up dotCMS with the following env var:

  DOT_FEATURE_FLAG_DB_UNIQUE_FIELD_VALIDATION: 'true'

• Make sure the unique_field table exists. So, run a CURL like this one:

  curl --location 'http://localhost:8080/api/v1/upgradetask' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Basic YWRtaW5AZG90Y21zLmNvbTphZG1pbg==' \
  --header 'Cookie: JSESSIONID=CF31A5750F5C83785EBC8EA3B8D8CF85; rme=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJqdGkiOiI0NjE3NmUxMi02YzJkLTQwNmMtYjcyNC00ZGZhYzQ1NjI1MTciLCJ4bW9kIjoxNzMyMTM2NTY5MzQyLCJzdWIiOiJkb3RjbXMub3JnLjEiLCJpYXQiOjE3MzIxMzY1NjksImlzcyI6IjM1NGNkOTg4NDQiLCJleHAiOjE3MzIyMjI5Njl9.A6rfTdWfSo-Sok7XcifcZAnJ6UMs6wtslLvuejeTfX0' \
  --data '{
  "upgradeTaskClass": "com.dotmarketing.startup.runonce.Task241007CreateUniqueFieldsTable"
  }'

• Create a test Content Type named My CT with two fields:
  • Site or Folder, named Site
  • Text, named Title, and marked as Unique, and add a Field Variable named uniquePerSite with the value of true.
• Create an empty Site named www.empty.com.
• Create two Contentlets of type My CT, with THE SAME VALUE for the unique field, but one living under demo.dotcms.com and the other one living under www.empty.com. They must be created without problem.
• Now, go to the definition of the Title field, and delete the uniquePerSite Field Variable.
• You'll see an error message and notifications indicating that the unique field cannot be recalculated, which is expected. This happens because both Contentlets you created have the same unique value.

No response

Sub-Tasks & Estimates

No response

[github-actions[bot]]

PRs:

• https://github.com/dotCMS/core/pull/30693
• https://github.com/dotCMS/core/pull/30730

[victoralfaro-dotcms]

Tested in dotcms/dotcms:trunk_e9c8559 After run curl command:

{"entity":"Ran the upgrade task: com.dotmarketing.startup.runonce.Task241007CreateUniqueFieldsTable","errors":[],"i18nMessagesMap":{},"messages":[],"pagination":null,"permissions":[]}

Logs:

dotcms-app-1  | 21:32:08.615  INFO  system.UpgradeTaskResource - Running the upgrade task: com.dotmarketing.startup.runonce.Task241007CreateUniqueFieldsTable
dotcms-app-1  | 21:32:08.703  INFO  system.UpgradeTaskResource - Ran the upgrade task: com.dotmarketing.startup.runonce.Task241007CreateUniqueFieldsTable

A Content Type was created with two fields: Title and Site. For the Title field we defined a field variable called uniquePerSite and it was set to true. Created a new site. Created two contents (of the recent created Content Type) one the demo.dotcms.com site and the other in the new site. Went to edit the Content Type and tried to delete uniquePerSite field variable. Error message when trying to delete the uniquePerSite field variable when there was already a content with the same unique field in a different site.

SHA before changes: d5c4e3130c61fd48ef51f5ac666d590d6186b77e24bbf76667960a2aee4694ae After manually removing the record holding the same unique field the deletion of the field variable was allowed and therefore the hash was recalculated. SHA after changes: 8db02dab81f332cf6bb24babbb39253063ce6569db7e32c3ced5758b9789d9ec

JSON after changes

[josemejias11]

Approved: Tested on trunk_e15f58e, Docker, macOS 14.5, FF v126.0.1