Categories” Page Displays Two Columns for Sub-Categories – Admin Panel

Open

#1,065 opened on Sep 3, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: javascript, react-native
Domain: frontend

Research direction

Start in the admin panel's Categories section and reproduce the duplicated sub-category columns in Chrome. Trace the data table schema or rendering logic responsible for the column headings, then confirm that only one clearly labeled sub-categories column remains and that category management is still usable.

Written by the indexing model from the issue text.

Description

Describe the bug
On the Categories page in the admin panel, there are two separate columns labeled or appearing as sub-categories, which creates confusion. This duplication is likely unintended and affects the clarity and usability of the category management interface.

To Reproduce
Steps to reproduce the behavior:

Navigate to the Categories section in the admin panel
View the columns listed for each category
Observe that two columns related to sub-categories are shown
Expected behavior
There should only be one column for sub-categories with a clear and concise label. If multiple sub-category columns are shown, they should have distinct purposes and proper headings to differentiate them.

Screenshots

Image

Desktop (please complete the following information):

OS: Windows 11

Browser: Chrome

Version: 123.0.6312.86

Additional context
This may be due to a UI rendering bug or misconfiguration in the data table schema. It can lead to administrative errors and should be fixed to maintain interface clarity.

App Version: [insert if known]

Additional context
This is likely caused by a layout padding/margin or rendering logic issue. Reducing this space will improve usability, reduce scroll effort, and provide a more polished UI appearance.

Dominant language: JavaScript
Stars: 2
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing 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.