In a bug report titled ‘Custom link suddenly no longer present’, ZeroDean reported that a custom profile link, previously visible in user cards, disappeared overnight. Initially suspecting a system update or bug, ZeroDean later realized it was a user error: the custom field name had been changed from ‘LinkedIn’ to ‘*LinkedIn’, which invalidated the link. pmusaraj had asked for clarification on how the link was being set, referencing the Custom Profile Link component. After realizing the mistake, ZeroDean apologized and thanked the team, noting they hadn’t updated the field name after the latest update. pmusaraj reassured them it was no problem. The issue was resolved without requiring code changes — it was purely a configuration oversight. The original post included a garbled sentence likely caused by accidental keyboard input or copy-paste error, which was later corrected. The thread highlights the importance of checking field names after updates and the helpfulness of community support in troubleshooting.
I installed this component a couple of weeks ago. It has been working very well since.
This morning, I noticed the custom link is no longer present in user cards. I swear it was there yesterday, but it could’ve been missing for the last 3 days (as suggested by the “Discourse updated: 3 days ago” in the admin panel). Otherwise, uncertain as to what would cause it to disappear.
I have tried turning it off and on again.
Thanks for letting us know, we will have a look this week.
What are you using to set custom links in user cards? This component: Custom Profile Link? I just tested that one locally, and it works correctly with latest core.
Aaaaah. User error. My apologies.
The field I’m using was formerly “LinkedIn” and got updated to be “*LinkedIn” without me realizing changing the field name would invalidate the link. Lesson learned. Had it not happened around the time of the latest update, I may not have been thrown off so easily.
Thanks for checking. I’ll be more careful.
No worries, thanks for the update.
This topic was automatically closed after 2 days. New replies are no longer allowed.