Skip to content

Bug 1545443: Remove the Splinter extension - #194

Open
topunix wants to merge 1 commit into
bugzilla:mainfrom
topunix:bug-1545443
Open

topunix wants to merge 1 commit into
bugzilla:mainfrom
topunix:bug-1545443

Conversation

@topunix

@topunix topunix commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1545443

Splinter is unmaintained and should not ship with Bugzilla 6. This removes extensions/Splinter and every reader of its splinter_base param:

  • Bugzilla/App.pm: the /review route
  • BugModal: the "Splinter Review" link on patch attachments
  • MyDashboard: the review link in the flags table and the template that set it
  • Review extension: the splinter page hook, and the request badge link (patches now link to the attachment details page, like other attachments)
  • global/header.html.tmpl: splinter_base in the JS params

Upgrade note: update_params does not drop params that are no longer defined, so upgraded installs keep a stale splinter_base value in data/params. Every reader is removed, so it is harmless; I left it rather than adding param cleanup code.

Tested locally in Docker, on a database that still has splinter_base set (the upgrade case):

  • t/004template.t passes
  • node --check passes on both edited JS files
  • show_bug with a patch attachment renders with no Splinter link
  • MyDashboard renders
  • /review returns 404

Splinter is unmaintained and should not ship with Bugzilla 6.

Remove extensions/Splinter and every reader of its splinter_base param: the /review route, the Splinter Review link on patch attachments in BugModal, the MyDashboard flag link, the Review extension's page hook and request badge link, and the param export in the global header. Patch links in the review badge now fall back to the attachment details page, as other attachments already do.

update_params does not drop params that are no longer defined, so upgraded installs keep a stale splinter_base value in data/params. Nothing reads it any more, so it is harmless and is left in place.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant