Store Logo, Banner, and Menu Not Displaying in Web App for Some Stores
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by reproducing the missing logo, banner, and menu in the Enatega web app, then compare the affected store's admin data with what the frontend receives. Check whether the failure is in API responses, asset paths or caching, or store-data filters. Done means configured store assets and menu content consistently appear in the web app.
Written by the indexing model from the issue text.
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.
- 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/food-ordering-system-java-eclipse
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
All issues in raymondjames090/food-ordering-system-java-eclipse
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