Can't hide or control access for Date TimeZone field

[skysarwer]

The following will not work :

...DateField(
              {
                name: "my_date",
                label: "My Date",
                required: true,
                defaultValue: () => new Date(new Date().getFullYear(), 0, 1),
                admin: {
                  date: {
                    displayFormat: "MMMM dd",
                  },
                },
              },
              {
                // here are the timezone settings
                enable: true,
                overrides: {
                  name: "my_timezone",
                  required: true,
                  defaultValue: "America/New_York",
                  admin: {
                    // this will not work
                    hidden: true,
                  },
                  // this will not work
                  access: {
                    update: () => false,
                  },
                },
              }
            ),

Being able to set overrides.access and overrides.admin.hidden to the timezone parameter of the field, and have the options impact the timezone select component would be amazing. custom alternative params outside of overrides would be an equally viable option.

We may not always want to allow the user to select a timezone, but just set one by default (and have it display that way accordingly).

A much nicer to have goal in this same vein would be if we could somehow set a timezone parameter to the date field based on the document data (such as different timezone fields, timezones within relationships, etc).

[jmtorres]

I'm also looking for this functionality. I previously implemented a separate timezone ACF field for our WordPress CMS. All of our datetime fields were stored separately based on the local time, and the frontend would handle the timezone conversion.

This is an example of how we handled it on that CMS:

We also had other post types (WP equivalent of Collections) that would reference the "post" with the timezone field. Those would have their own datetime fields that would also base their timezone on the reference.

As an example, we would have an "Event" that occurs at a specific location within a particular timezone. That event could have multiple "Event Schedules", "Performances", "Sessions", etc. Each of those collections has datetime fields that would benefit from sharing the timezone of the referenced "Event".