Unintended Toggling of Buttons in "Restaurants Section" Section of Admin Dashboard

Open

#1,491 opened on May 4, 2026 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: 48/100

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

Research direction

Start by reproducing the problem in the Admin Dashboard's Restaurants section using Chrome, following the listed toggle steps. Trace the Restaurants section entry point and its toggle state handling to identify why unrelated buttons change; done means toggling one restaurant setting leaves every other button unchanged.

Written by the indexing model from the issue text.

Description

Describe the bug
In the Enatega Multivendor Admin Dashboard, specifically in the "Restaurants section" section, there is an issue where toggling one button on or off intermittently triggers the system to toggle other buttons that were not intended to be changed. This behavior is unexpected and can lead to unintended changes in the settings of restaurants, causing potential confusion and errors in the admin interface.

To Reproduce
Steps to reproduce the behavior:

Log in to the Enatega Multivendor Admin Dashboard.
Navigate to the "Restaurants section" section.
Attempt to toggle a specific button (e.g., enable/disable a feature) for a restaurant.
Observe that other buttons in the vicinity may also be toggled without explicit user interaction.
Expected behavior
Toggling one button in the "Restaurants" section should only affect the state of that specific button, and other buttons should remain unchanged unless explicitly modified by the user.

Screenshots
https://github.com/ninjas-code-official/food-delivery-multivendor/assets/152266796/b81cddc8-08ac-4f08-9c55-606b75035a22

Desktop:

Browser: chrome

Dominant language: JavaScript
Stars: 0
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.