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

Check: files linked from menus may not count as used

Open
#204 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
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
backend

Research direction

Read packages/builder-server/src/services/mediaUsageService.js around lines 536–732 and packages/builder-server/src/controllers/menuController.js; first confirm whether the menu link UI accepts typed upload paths. If it does, trace full and targeted media usage scans and add coverage for menu links; if it does not, document that finding. Done means the menu path either blocks deletion in both scans with a test, or is shown not to support upload paths.

Written by the indexing model from the issue text.

Description

Check first: a file linked straight from a menu (for example a PDF brochure) may not count as "used", so it can be deleted while the menu still links to it.


mediaUsageService.js (~536-732) scans pages, globals, theme settings, site identity and collection items in every language, but not menus/**, and there is no per-menu sync. A menu link typed as /uploads/files/brochure.pdf doesn't block deletion, while the same link in a widget does. Predates 0.9.10. First confirm the menu link UI accepts typed upload paths.

Done when: Either menus are scanned (full and targeted) with a test, or menu links are shown not to carry upload paths.

Start: mediaUsageService.js, menuController.js. Source: 2026-10-05 code review of 48eef6f4..9e98dad7.

Dominant language
JavaScript
Stars
162
Forks
6
Avg merge
12h 55m
Merged PRs (30d)
2

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 tsiger/widgetizer

All issues in tsiger/widgetizer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.