Closed (won't fix)
Project:
Profile
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 Aug 2018 at 16:53 UTC
Updated:
18 Apr 2019 at 04:20 UTC
Jump to comment: Most recent
Comments
Comment #2
kclarkson commentedI am also having this issue. We are using a different admin theme and is confusing to the user when they go to enter their profile information.
Comment #3
kclarkson commentedComment #4
matzab commentedSame problem here. It's very confusing for a content editor if he/she ist editing profiles and finds him-/herself in a different editing theme.
Comment #5
mglamanRetitling
Comment #6
bojanz commentedIt feels very jarring to send the user to the admin theme just so that they can edit their address.
TBH, I don't really know why this was done for user edit either.
Comment #7
mglamanI was ready to push this as "won't fix" or "works as designed." However, if the user does not have permission to view the admin theme, they always see the frontend theme. This just keeps parts inline with the admin experience. However, they'd jump from frontend theme to list profiles and then admin to edit -- at least or multiple.
End users shouldn't see the admin theme, so this only is troublesome to admins.
Comment #8
mglamanI am going to won't fix this. I'm aware the user edit form is flagged as an admin route, but that does not mean profile routes should be.
If you feel different, you can implement a RouteSubscriber to alter the routes and flag them. See https://www.drupal.org/docs/8/api/routing-system/altering-existing-route...