Check: site-wide links in theme settings may ignore the page language
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 56/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- internationalization
Research direction
Start in packages/render-engine/src/renderEngine.js, especially resolveThemeSettingReferences around lines 760–860, and trace how theme-setting links and menus are resolved before currentPageData is set. Check how rendering language is available for translated pages. Done when references resolve for the page language, or the theme contract documents the limitation.
Written by the indexing model from the issue text.
Description
Check first: on translated pages, a link or menu picked in a theme's site-wide settings may still point to the main language.
resolveThemeSettingReferences (renderEngine.js ~760-860): a theme-setting link resolves to the target's own language and a uuid menu to that exact menu; theme.json is one file for all languages, so Greek pages show English targets (the leak d0442659 fixed for page_url). On item pages theme settings resolve before currentPageData is set, so a slug menu resolves to the root-language menu. Arch declares no such settings, so third-party themes only.
Done when: Theme-setting references resolve per rendering language, or the limitation is documented in the theme contract.
Start: renderEngine.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
- 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 tsiger/widgetizer
-
question
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
tsiger/widgetizer#194 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
tsiger/widgetizer#181 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
tsiger/widgetizer#175 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
tsiger/widgetizer#174 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tsiger/widgetizer#173 ·
All issues in tsiger/widgetizer
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/open-webui#33196 · 2 comments ·
Maintainers usually reply within 1 day
-
area: apple-music area: build-release bug effort: small priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ChristianTabor/Argon#32 ·
Maintainers usually reply within 1 day
-
0️⃣ phase/new
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100