Enatega Admin Dashboard: Error Message Displayed When Adding a New Banner and Linking It to a Specific Restaurant
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
No source files or failing tests are identified. Start by reproducing the issue in the Enatega admin dashboard while adding a banner for one restaurant, then inspect the submission error and the related banner-management entry point. Done means the banner saves successfully and remains linked to the selected restaurant without an error.
Written by the indexing model from the issue text.
Description
Describe the bug
When a user tries to add a new banner and assigns it to a specific restaurant, an error message appears during submission. As a result, the banner either fails to save or does not link properly to the selected restaurant. This disrupts banner management functionality and limits restaurant-specific promotions.
Steps to Reproduce:
Log in to the admin panel or banner management section.
Click Add New Banner.
Fill in all required fields (e.g., image, title, etc.).
Select a specific restaurant from the dropdown or list.
Click Save or Submit.
Observe the error message displayed.
Expected Result:
The banner should be created successfully and linked to the selected restaurant without any errors.
Actual Result:
An error message appears, and the banner may not be created or properly linked.
Desktop (please complete the following information):
OS: [e.g. Windows]
Browser [e.g. chrome]
Version [e.g. Latest]
Labels: Enatega Multivendor Admin Dashboard, High Priority, Bug
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from raymondjames090/uber-eats-app-clone-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2069 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2003 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raymondjames090/uber-eats-app-clone-using-react-native#2002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#1979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
raymondjames090/uber-eats-app-clone-using-react-native#1978 ·
All issues in raymondjames090/uber-eats-app-clone-using-react-native
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100