Admin plugin catalog lists deprecated and archived plugins

Open
#8,246 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
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
tooling

Research direction

Start in src/static/js/pluginfw/installer.ts, especially getAvailablePlugins and the code that reads ${settings.updateServer}/plugins.json. Trace how catalog entries become the admin “Available plugins” list and check the existing plugin feed shape. Done means deprecated or incompatible plugins such as ep_adminpads2 are no longer offered, with coverage in the relevant installer tests if they exist.

Written by the indexing model from the issue text.

Description

Found while triaging ether/ep_adminpads2 issues.

getAvailablePlugins (src/static/js/pluginfw/installer.ts) builds the admin "Available plugins" list from ${settings.updateServer}/plugins.json with no filter for deprecated or unmaintained packages. An admin can therefore install a plugin that is known to be broken on current Etherpad.

Concrete example: ep_adminpads2 is archived upstream and obsolete (core's own Manage pads page replaced it). Installing it breaks the working admin page: the plugin registers /admin/pads before core's route, and its old template needs JS files core no longer ships, so the page hangs on "Loading…" with $ is not defined. Reproduced on 3.3.5 with ep_adminpads2@2.1.110.

Suggested fix: have the catalog skip packages npm marks deprecated, and/or let the plugin feed carry a compatibility range so plugins that don't support the running version aren't offered.

Dominant language
TypeScript
Stars
18.6k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
78

Contributor guide

Open the 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 ether/etherpad

All issues in ether/etherpad

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.