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:

  1. 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.
  2. 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.
  3. li

Comments

doitDave’s picture

Issue summary: View changes

Anyone feel free to vote (and argue) for one of these options. I personally tend to a separate table with D8 in mind.