Let’s say you want to add a link of User’s main profile page on Discourse user profile page and user card, clicking on that link will take user to main (external) website.
The link of main website user profile page will be like:
http://site.com/username
Where username is the Discourse username of that user. (It should be same on both main site and Discourse forum)
Let’s get started!
Add custom CSS
Paste this CSS code in Admin > Customize > CSS/HTML > CSS section:
Dear Arpit, does this approach really update userfield siteLink?
We used it “as is” and siteLink in empty under user/preferences siteLink although it is visible over user card
thx
Any chance this example could get an update? Apparently it will not work, since api.container.lookupFactory is a private API and will break stuff
I asked the same a long time ago. You’d have to write a plugin that exposes external_id - I asked recently if it had become enabled, since they changed a lot of stuff, but haven’t received an answer, so I guess it still requires a plugin…
@techAPJ, this code is great. I want to make one small tweak and perhaps you know… how can I get the external_id at the end of the URL (i.e. const url = 'http://site.com/${external_id}')? I tried changing the code to pull external_id from the user object but it says that property is undefined.
This code is deprecated, can you update it please? I tried to tweak it but it didn’t work.
[Admin Notice] One or more of your plugins or theme components needs to be updated because it is incompatible with Discourse 3.2.
More information can be found in the Communiteq knowledge base.
Details: [THEME 1 ‘Default’] Function prototype extensions have been deprecated, please migrate from function(){}.property(‘bar’) to computed(‘bar’, function() {}).
It looks like this is very similar to another guide. As with that one, the strategies suggested in the OP are extremely out-of-date. The best thing going forward is going to be to build the functionality into a git-managed theme component, so that people don’t need to copy/paste code.
We’re looking at whether we can create an official theme-component to cover both use cases, and will update both the topics if/when that’s ready.