Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Currently, the server based fieldset statuses are stored with the user entity. This can lead to confusion if a user is active on multiple sites (e.g. a multisite with a shared users table) as the internal "cuids" (collapser unique ids, for form/fieldset combinations) can differ from site to site. The reason is that they are created randomly on first appearance ("first come first served").
Options:
- Store all collapser data in a per-site table (as the cuids).
Advantages:
- $user->data is deprecated anyway, so this is a step towards D8.
Disadvantages:
- Major design change, would require a new branch.
- Change random cuids into an md5 hash.
Advantages:
- No major design change.
Disadvantages:
- Continuing a deprecated method.
Neutral/unclear:
- Form states would be shared across all sites - which may be plus. Or minus.
li
Comments
Comment #1
doitDave CreditAttribution: doitDave commentedAnyone feel free to vote (and argue) for one of these options. I personally tend to a separate table with D8 in mind.