Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Enable/Disable Buttons Not Functioning Properly in Enatega Multivendor Admin (Restaurant Section)

Open
#191 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
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
react, typescript
Domain
frontend

Research direction

Start by reproducing the issue in Chrome using the Admin Restaurant section and the listed enable and disable steps. Trace the controls from the restaurant interface through the status update flow. Done means enabling makes a restaurant visible and accessible, while disabling makes it temporarily unavailable and the displayed status changes.

Written by the indexing model from the issue text.

Description

Describe the bug
In the Enatega Multivendor Admin, specifically in the restaurant section, the enable and disable buttons are not functioning as intended. This issue is hindering the ability to manage the status of restaurants effectively.

To Reproduce
Steps to reproduce the behavior:

Log in to the Enatega Multivendor Admin.
Navigate to the "Restaurant" section.
Attempt to use the "Enable" and "Disable" buttons to change the status of a restaurant.
Observe that the buttons are not working as expected, and the status remains unchanged.
Expected behavior
The "Enable" button should activate the restaurant, allowing it to be visible and accessible. The "Disable" button should deactivate the restaurant, making it temporarily unavailable.

Screenshots
https://github.com/ninjas-code-official/food-delivery-multivendor/assets/152266796/5751c2e4-57fc-430c-948d-233d36fefc19

Desktop:

Browser: chrome

Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from patriciaperez90/document-solution-application-react

All issues in patriciaperez90/document-solution-application-react

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.