Margaret-Petersen / Margaret-Petersen/uber-eats-clone-android
Store Logo, Banner, and Menu Not Displaying in Web App for Some Stores
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
In the Enatega web app, some stores are not displaying their logo, banner image, or menu content, even though all relevant data appears correctly configured and visible in the admin panel. Affected stores appear incomplete or broken in the frontend, which disrupts the user experience and may reduce engagement or orders.
To Reproduce
Steps to reproduce the behavior:
Open the Enatega web app
Navigate to one of the affected stores
Observe that the logo and banner images are missing, and the menu items are not shown
Verify in the admin panel that the store has all assets and content properly set
Expected behavior
All store data—including logos, banners, and menus—should be fetched and displayed correctly on the web app if it exists in the admin.
Screenshots
Recording 2025-06-18 115630.zip
Desktop (please complete the following information):
OS: Windows 11
Browser: Chrome
Version: [e.g., 123.0.6312.86]
Additional context
This issue may be caused by API failures, content delivery issues (e.g., broken image paths or caching), or filters incorrectly applied to the store data. It should be prioritized as it impacts visibility and sales potential for affected vendors.
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
No source files or tests are named. Reproduce the problem in the web app with an affected store, compare its data with the admin panel, and trace the store data and asset display from the relevant frontend entry point; done means the logo, banner, and menu appear when configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100