[Content Import] : Charset from import file cannot be determined
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Parent Issue
Found when doing the QA on ticket:
- #31692
Problem Statement
There's an error being logged when trying to import Contentlets using the CSV file. Even though the import process is working as expected, the error is adding a lot of unnecessary data to the log.
Steps to Reproduce
Refer to the video in ticket #31692 , and use the following CSV file for importing test Contentlets:
Acceptance Criteria
If you're using a valid CSV file to import content, no error should be logged.
dotCMS Version
Latest main.
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reproduction video and parent issue #31692, then import the provided TestUniqueFields.csv file and inspect where the charset-detection error is logged. Confirm the valid import still succeeds and that no error is logged for the CSV.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100