This proposal is about stripping all non-account options from the 'Account settings' configuration page and moving them to a new configuration page below 'People' called 'Account workflow'.
Demo 2 (previous, but still very close, new demo soon)
Demo 1 (previous) (with a bunch of demo fields that are not part of any patch yet, but just exist to showcase the concept a bit).
I have been doing some work on the registration / authentication process in contrib space last couple months and found that, while being very flexible already, there are some areas that i feel could use some love. Some people say the registration process lacks a couple basic functions lots of other systems support, or at least a more structured way to configure it all. And not that we need to copy behaviour, or be like them, but I would like to propose to stay close to the people that actually have to use Drupal (end-users). While Drupal 7 is already a major step in the right direction, i believe we can do more, if only to offer more flexibility for site owners/administrators to change the registration workflow features, without having to start coding. (i'm taking about very basic thing here, like forcing a password field on registration, forcing people to change their passwords after using a one-time-login link, e-mail field confirmation on registration by adding an extra e-mail field on the form (people (end-users) are pretty used to that by now), and so on.) These are minor tweaks and features, but if you put them all together, you got a pretty nice stack of highly flexible options. (Features in this context has nothing to do with the 'features' module, nor does the 'context' module has anything to do with this line of text.) (just to be clear)
Another thing i myself believe could use some love, is the idea to provide a real 'home' for all known authentication/registration/cancellation/etc modules. There's a long list of 'package's modules use to define the group they belong on on the modules page, but even worse, the configuration page is getting larger and larger if you install just a couple of these modules. Why? They are not only placed under 'people', but also under 'system', a completely 'new' entry, with separate menu items (because the dev didn't figure out the fine details for context menu items), and so on. Why does this happen? Because developers dont find the 'people' page the correct place for their module's options/config page, or they just dont know, or the project is to big/complex to put it below 'People', etc, etc. For node type options it is so clear for everybody where to place their module's options, but for registration/auth/cancel options this structure doesn't exist.
So another part of the idea also includes providing a place where core could stash the account workflow options in a more flexible setup, including contrib module options. This way it's easier for contrib module developers to know where to place their module's options and site owners / administrators have 1 place to look for these options.
Let' start with a "Before picture":
This is how the current Account settings page looks like in Drupal 7. In Drupal 8 this didn't change much yet, but i see issues in the queues that will expand this page, making it even longer.
While i already received 1 comment about this proposal possibly getting to complex, i would like to react that having a page with a lot of stuff on it just isn't the right way and i also think it's even more complex in a lot of cases, how people experience it. And not only that, next to this you have tablets, mini laptops, etc. People are overloaded with info and options; that's just how we human beings work (or at least a large part of the group). Nothing against that; that's just how it is, but we can tackle this i believe (at least for a large part).
(I believe the system e-mail templates also have nothing to do with user account settings whatsoever, nor the registration/cancellation process. To be honest, i actually believe the 'E-mail templates' also do not belong on the 'Account workflow' page, i moved it to a separate item below system, see the current demo and screenshots.)
After pictures:
I've created 3 albums. The first shows the fully functional demo that's active on my test server with all possible bells and whistles enabled and the second is the previous version of the patch, from before i created a simple and advanced option and forms. The third album contains a combination of new input / new ideas we can unleash on this concept. This album is created from the current patch.
Stage 1 (Drupal 8)
Stage 2 (Drupal 9)
But it would be great to have it in D8, or at least a basic version, we can later upgrade in D9.
Very much related to this proposal: (but not required)
I hope / guess that in the next couple days / weeks (at least) a couple of the related patches that are linked here will be commited.
Other:
The patch now creates 2 versions of the accounts config page:
The simple version is a minimal-click system, where you only have to click a minimum number of times to just set it to a working mode that works for like ?% of all people using Drupal. (simple mode would/should also be able to set some pretty interesting settings, all depends on how much 'site access profiles' we create and how complex they will be.) The questionmark? I'm not sure, but 60%? At least. (if i have to guess, but could be a lot higher)
Real tweaker can then still dive into the advanced config and set values according to their case. They access the advanced setting via a config option on the simple config page.
Closed: outdated
11.0 🔥
user.module
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
There has been no discussion here for 12 years, and of course, things have changed a bit in those years. Due to the lack of activity I am going to close this issue.
If there is anything in this issue that still need work, open a new issue and let's start fresh. As always, search for a duplicate issue first.
Thanks.
