User timezone should be available as a token

why is this being done in the patch?
+ $account->set('timezone', 'America/Santiago');
If you are using the $user->id, should that user's timezone be used first, then the default of the site be the fallback?

Re-rolled against 8.7. Not sure if this will work for 8.8 but I figured I still upload the patch since we need it for a project running 8.7.

Setting back to Needs Review & Triggering bots. Verified that above patch still applies to 8.8.x branch.

Thank you for working on this everyone.

While testing I've used the Token Filter module.

After setting up the text formatter to use tokens, I created a new basic page and the following:

All times are shown as timezone of [current-user:timezone]

Your email address is [current-user:mail]

Before patching:

After patching:

And the timezone is updated when the user changes their locale settings.

Unfortunately the new token does not appear in the token list:

To do this, the user_token_info() function needs to be updated to include the new token.

A change record needs to be drafted as well.

Both these tasks can be novice task, so I've set that tag, and returned the issue to needs work.

Hi, I will try to finish the patch and write the API change record.

I take the pacth 12 and I add to user_token_info() the information about the new token as requested in comment #14.
This is a screenshot of the result in the help page (admin/help/token).

I will write the API change record draft now.

I have created the change record draft.
link here

Needs patch (or MR) against 9.3.x

A re-rolled patch against 9.3.x. Please review.

1. +++ b/core/modules/user/user.tokens.inc
   @@ -138,6 +142,11 @@ function user_tokens($type, $tokens, array $data, array $options, BubbleableMeta
   +          // Fallback to system default timezone, as timestamps are localised.
   

   Try 'localized'. Drupal's code standards specify "American English" is to be used in the codebase (CSpell custom command error).
   
   

2. The draft change record is not yet fit for purpose. It needs to describe the change, including how it affects site behaviour. Looking at other published change records is a good way to get an idea of the desired output.

Command failures have been fixed in the updated patch i.e point 1.

Also please elaborate more if point 2 need to have any update to the codebase.

@akshay_d, a change record doesn't need to have an update the codebase itself. See Write a change record for a Drupal core issue.

I edited the issue summary so next steps are clear.

I briefly reviewed the patch above.

+++ b/core/modules/user/user.tokens.inc
@@ -63,6 +63,10 @@ function user_token_info() {
+    'name' => t("Timezone"),
+    'description' => t("The timezone of the current user account."),

We should use single quotes here.

After that is fixed, I think that you can add the "Needs manual testing" and "Needs issue s

Applied #25 patch working fine and looks good for me
After patch user time zone field is added in token

Thanks for the patch
For ref sharing screenshots .....

Updated patch #25 as per mentioned in #27

Thank you for manually testing and uploading the screenshots, @vikashsoni! The final step for completing a manual testing task is to add the before and after screenshots to the issue summary replacing any old screenshots. I modified the issue summary in order to complete that last step.

+++ b/core/modules/user/user.tokens.inc
@@ -64,8 +64,8 @@
-    'name' => t("Timezone"),
-    'description' => t("The timezone of the current user account."),
+    'name' => t('Timezone'),
+    'description' => t('The timezone of the current user account.'),

Thank you for the patch, @karishmaamin! The minor code standard fix looks good to me.

I noticed that this introduces a new translatable string. I looked on localize.drupal.org and found "The timezone of this user.", but I don't think that fits with the other token descriptions which call out "user account" rather than "user". Also, the word "current" isn't used for most of the user token descriptions. I think the we can drop the word "current" as it might be confusing when compared to the other strings. I'm going to bump it back to Needs work for that change. I'm sorry I didn't think about the wording in my previous review.

We still need to modify the draft change record per @darvanen's review in comment #24.

Addresses #29 && Attached patch against Drupal 10.1.x

Per #24

Removing Novice tag until some of the specific reviews are complete.

What is the current status of this issue? The patch no longer applies for D11.

@bob.hinrichs you can usually figure that out by working back through the comments. In this case the latest status change is at #37, referencing #24 which hasn't been addressed. We'll need to add rebasing the MR to the list of tasks too.