Quantcast
Channel: Issues for Drupal core
Viewing all articles
Browse latest Browse all 298064

Join language and timezone settings in one single fieldset and move user code out of system.module

$
0
0

Problem/Motivation

The user profile edit page, user/%uid/edit, has a field set for language settings and another one for locale settings. I don't think this is necessary and they should be joined together in one field set labeled 'Locale settings', because language and timezone are actually locale settings. So they should be joined in one field set to clean up the form a bit. This has been the case since Drupal 5.1, where at that time the system.module and locale.module each define their own field set on the user account settings page.

Proposed resolution

  • Create one field set for locale settings.
  • Locale setting also seems to be a really bad UX, Localization is a bit better at least and actually is more descriptive of what it does.

Remaining tasks

Review
Usability review
Commit
Enjoy!

User interface changes

Screenshots

Before Monolingual
Before Multilingual
After Monolingual
After Multilingual

API changes

Data model changes


Viewing all articles
Browse latest Browse all 298064

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>