[Self Hosted] User traits are not being read from limit configs

(#3490) Bug Fixed

6d agoby RexSystem originally by @kaibsora on GitHub

Reproduction steps

Go to limit config, create a new trait with limits modified, such as bio length. give it a filter rule apply filter rule to user under user account tab in admin center reload the logged in users page or clear cache and see that the settings for the field limits are the exact same as before adding the trait to the user. ie, no change

Observed behaviour

When setting a trait on a user, ie "vip", this trait seems to not apply or get read during user functions. Limits do not get applied. Even setting the base "premium" trait does not see it apply.

Build information

Stable Web 2026.1005.184833, Linux (x64), Firefox 149.0, Locale en-US

Platform

Self-hosting

Evidence

image image image image

3 comments

RexSystem 1 vote 23h ago

Fixed in the self-hosted api 2026.1011.113345: limit rules for user traits are read again, and edits survive premium model switches.

Permalink

FantasyDragon14 1 vote 4d ago edited

cannot reproduce on Stable Web 2026.1007.140812, Linux (x64), Firefox 153.0, Locale en-GB our custom limits are correctly applied we use stock deployment, from before the install script but migrated & updated with it

Permalink

dander 1 vote 5h ago

Can still reproduce with the same steps. Updated my self-hosted instance to the latest version. Tried using a separate browser to avoid caching. (My instances premium model is set to everyone)ran into some similar issues, have made a report for them here: #3919 Canary Web 2026.1012.2059, Linux (x64), Firefox 157.0, Locale en-US

Permalink