Route conflict on fingerprint plugin

[RGJ (Richard - Communiteq)]

Continuing the discussion from Discourse Fingerprint - Browser Fingerprinting Plugin:

@Overgrow

Following up on the deprecation above.. on current core (v2026.8.0-latest.1) it’s not just a warning any more, the report page itself looks broken.

/admin/plugins/fingerprint comes up with an empty “latest matches” and flagged list, and the console throws:

Uncaught (in promise) TypeError: Cannot convert undefined or null to object
    at Object.values (<anonymous>)
    at fingerprint-report.js:58

This is happening because of a route conflict.

Core defines

admin_plugins GET /admin/plugins/:plugin_id(.:format) admin/plugin#show {format: /(json|html|\*\/\*)/}

The plugin defines this

admin_plugins_fingerprint GET  /admin/plugins/fingerprint(.:format) discourse_fingerprint/fingerprint_admin#index

Instead of returning the results from the fingerprint_admin#index, we get the results from the admin/plugin#show controller, i.e. the plugin metadata.

there are a few more issues in this plugin like the route format deprecation

@Roi

DEPRECATION NOTICE: Looking up ‘route:admin-plugins-fingerprint’ is no longer permitted. Rename to ‘route:admin-plugins/fingerprint’ instead [deprecation id: discourse.deprecated-resolver-normalization]

and the plugin.rb metadata pointing to the old URL for this plugin # url: https://github.com/udan11/discourse-fingerprint.git

[WorldIsMine (DaveK)]

Richard Richard he’s the man, if he can’t do it no one can! Yaaaay! So no more annoying errors?

[RGJ (Richard - Communiteq)]

PR here Resolve route conflict and small fixes - Pull Request #95 - discourse/discourse-fingerprint - GitHub