The discussion focuses on the Discourse Profile Custom Link theme component, developed by chapoi. This tool adds a customizable link to user profiles and usercards, allowing administrators to define a prefix URL (e.g., GitHub profiles) that appends either the username or a specific user field value. mattdm raised concerns about security, questioning if links receive nofollow attributes or are scanned by Akismet to prevent spam.
Users noted minor issues and improvements. Firepup650 pointed out a typo in the documentation (github/com vs github.com) and questioned the use of http over https, which the developer confirmed was an oversight. Julian2 requested a native Discourse feature allowing clickable links in user fields, rather than relying on a plugin. chapoi explained that user fields are primarily text-based and do not automatically render links, suggesting a feature request instead. Consequently, Vaping_Community submitted a feature request for a clickable URL user field type.
Technical troubleshooting followed, with Joseph_Tucker1 reporting issues with trailing slashes in URLs and difficulty converting the plugin to a theme for JavaScript modifications. RGJ reported the component stopped working on version v2025.11, citing a deprecation warning for array.filterBy. chapoi clarified that deprecation warnings do not necessarily cause failures, and RGJ later confirmed the issue was due to user error.
Finally, Web_SWLT encountered an “Admin Notice” about outdated Handlebars extensions (.hbs). david discovered that Web_SWLT had installed a similarly named fork (custom-profile-links) instead of the original (custom-profile-link). Moin directed users facing deprecation warnings in the forked version to the Multiple Custom Profile Links component, noting that a pull request exists to fix the deprecated code.
Yeah, that’s actually a fair point you bring up. I’ll look into the possibility of your suggestion; my guess is that there is a reason why that wasn’t done, but I don’t know atm.
So, I had a look but the necessary changes are way above my designer skills (read: backend databas-y stuff) – so I’m afraid it will be necessary to use the plugin.
An option you could consider is making a feature request, and seeing if that garners more interest.
This solution is great and I hope we can help improve it. Our profile link is of the form “https://www.domain.com/user/[USER-ID]/”. The trailing slash wrecks the solution for us. I can add a URL rewrite but a better solution would be to make the code more adaptive. I want working real links back to the site!
I tried to convert the plugin to a theme so I could improve the javascript but that CONVERT Discourse function doesn’t seem to be working.
Can you make the update so that it adds functionality?
This component seems to have stopped working on v2025.11
[THEME 2 'Custom Profile Link'] Deprecation notice: The array.filterBy is a deprecated Ember native array extension. Use native array methods or a TrackedArray instead. [deprecated since Discourse 3.6.0.beta1-dev] [deprecation id: discourse.native-array-extensions.filterBy]
I have installed this and it’s exactly what I need to allow my members to link from their Discourse account to their member profile on our website. As an admin though, I’m seeing a warning: [Admin Notice] Theme ‘Custom profile links’ contains code which needs updating. (id:discourse.hbs-extension) (learn more) . Is this the appropriate place to ask for help in updating?
Could you double check you’re using the theme-component linked in the OP @Web_SWLT? I wonder if you have a similarly-named version from a different author