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

FileAssetContainers not found when using case #30457

Closed
erickgonzalez opened this issue Oct 25, 2024 · 3 comments · Fixed by #30543
Closed

FileAssetContainers not found when using case #30457

erickgonzalez opened this issue Oct 25, 2024 · 3 comments · Fixed by #30543
Assignees
Labels

Comments

@erickgonzalez
Copy link
Contributor

Parent Issue

No response

Problem Statement

In the Template Portlet, FileAssetContainers are not consistently listed when searched for with the case they were originally created in. This leads to an issue where users can only locate FileAssetContainers by using lowercase search terms, regardless of the original case. This inconsistency may result in user frustration, reduced efficiency, and potential confusion, as users might not find the assets they are looking for if they don’t use lowercase during the search.

NOTE: This only happens to FileAssetContainers; for normal containers, it finds them regardless of the case used.

Steps to Reproduce

1- Create a FileAssetContainer with the title UPPERCASE
2- Go to the Templates Portlet
3- Create a new design Template
4- Try to find the created container by typing UPPERCASE
5- Nothing is found
6- Try to find the created container by typing uppercase
7- Container is found

Screen.Recording.2024-10-25.at.10.08.22.AM.mov

Acceptance Criteria

Regardless of the case used to search the containers, they should return.

dotCMS Version

24.04 LTS
demo (24.10.16)

Proposed Objective

Customer Support

Proposed Priority

Priority 3 - Average

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

https://dotcms.freshdesk.com/a/tickets/28191

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

If you search for them in lowercase, it finds them

Sub-Tasks & Estimates

No response

@dsolistorres dsolistorres moved this from In Progress to In Review in dotCMS - Product Planning Oct 31, 2024
github-merge-queue bot pushed a commit that referenced this issue Nov 12, 2024
… file containers (#30543)

Closes #30457

### Proposed Changes
* Modified the `findFolderAssetContainers` method to ensure container
name searches are case-insensitive

### Checklist
- [x] Tests

Co-authored-by: erickgonzalez <[email protected]>
@github-project-automation github-project-automation bot moved this from In Review to Internal QA in dotCMS - Product Planning Nov 12, 2024
@erickgonzalez
Copy link
Contributor Author

Working as it should, now you can search file asset containers regardless of the case.

Screenshot 2024-11-13 at 10 49 00 AM

Screenshot 2024-11-13 at 10 48 46 AM

Screenshot 2024-11-13 at 10 49 23 AM

@erickgonzalez erickgonzalez moved this from Internal QA to QA - Backlog in dotCMS - Product Planning Nov 13, 2024
@bryanboza
Copy link
Contributor

Fixed, now it is working as expected
Image

@erickgonzalez erickgonzalez added the LTS: Needs Backport Ticket that will be added to LTS label Nov 14, 2024
@erickgonzalez erickgonzalez added the LTS: Next Patch Shortlisted of issues that will be included in the upcoming LTS patch label Nov 28, 2024
gortiz-dotcms added a commit that referenced this issue Dec 5, 2024
erickgonzalez added a commit that referenced this issue Dec 5, 2024
@erickgonzalez erickgonzalez added Release : 23.10.24 v20 Included in LTS patch release 23.10.24 v20 Release : 24.04.24 v12 Included in LTS patch release 24.04.24 v12 and removed LTS: Needs Backport Ticket that will be added to LTS LTS: Next Patch Shortlisted of issues that will be included in the upcoming LTS patch labels Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants