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.
There is still some legacy code in theme.inc that checks if a user's custom theme (support for which was removed in D7) should be loaded. The database field that stores it is still present, as well as a test that checks if said properly exists on a newly created user object.
Identical for D7.
Comment | File | Size | Author |
---|---|---|---|
#6 | 1814880-user_theme-6.patch | 1.1 KB | grisendo |
#4 | 1814880-user_theme-4.patch | 2.4 KB | cafuego |
#1 | 1814880-1.patch | 2.58 KB | cafuego |
Comments
Comment #1
cafuego CreditAttribution: cafuego commentedAttached is the patch for D8.
Comment #2
cafuego CreditAttribution: cafuego commented#1: 1814880-1.patch queued for re-testing.
Comment #4
cafuego CreditAttribution: cafuego commentedUpdated patch against current 8.x HEAD.
Comment #5
areke CreditAttribution: areke commentedThe patch doesn't apply anymore, so it needs to be rebased against the current HEAD.
Comment #6
grisendo CreditAttribution: grisendo commentedRe-rolled
Comment #8
dawehner@grisendo
In general, we no longer add update functions but work on migrations as far as I understand it.
Comment #11
dpiThis is no longer an issue with D8.
In transition to user entity, the 'theme' table property did not come along for the ride.
Marked as outdated.
Comment #12
dpiChange to D7