[Containers] : Clicking a Container as File is not taking you to the right location in the Site Browser

[jcastro-dotcms]

Parent Issue

No response

Problem Statement

In the Containers portlet, when users want to edit any Container as File, they click its name and are taken to the Site Browser portlet to the exact location of such a Container. This is not working right now.

Steps to Reproduce

• Log into dotCMS, with the Full Starter.
• Go to the Site > Containers portlet.
• Click either the default or banner Container -- which are the only Containers as Files in the Full Starter.
• The Site Browser portlet is neither opening the expected folder nor displaying its contents.

Acceptance Criteria

Clicking any Container as File must take you to the Site Browser portlet in its expected location.

dotCMS Version

dotCMS 23.05

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

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

Found when working on ticket: #23798

Assumptions & Initiation Needs

There are two columns in the folder database table named inode and identifier. In recent versions, when you create a folder, both columns have the value of the folder's Identifier.

However, in older versions, a folder had a specific Inode and Identifier, which were not the same. We need to fix this inconsistency. Maybe an Upgrade Task can take care of this.

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[jcastro-dotcms]

NOTE TO QA:

• Use the Full Starter so that it's easier to create dummy Containers as Files.
• Make sure that the existing default and banner Containers are now being displayed and selected properly in the Site Browser.
• You can use Admin and Admin2 to hace two Users accessing the same dotCMS instance. Each User should only see the folders they selected or expanded.
• After logging out and back in, the folder tree should all be collapsed.

[bryanboza]

Fixed, tested on release-23.05 // Docker // FF