Problem/Motivation

Currently you cannot add scheduling fields in the user interface. This makes sense, because the access-checking logic is bound to the presence of the field and it doesn't make sense to have multiple of those.

Theoretically people may want to use the scheduling logic however, to just display a list of upcoming events, for example, without any access-control ramifications.

Proposed resolution

  1. Make the "scheduling access control" feature a field storage setting and set enable that for the automatically-generated field storage definitions
  2. Remove the "no_ui" flag from the field and make sure that the setting is disabled for user-created fields
  3. Consider whether we need more/better formatters for this to make sense, and, if so, implement them

Remaining tasks

User interface changes

API changes

Data model changes

Comments

tstoeckler created an issue. See original summary.

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented

Just wanted to open this to discuss this. I'm fine with not actually implementing this, not 100% sure myself that it makes sense, but I had thought of the possibility, so, yeah, makes sense to talk about this.

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented
Issue tags: +DevDaysAthens2026

Discussed this with @chr.fritsch, @daniel.bosen and @jan.stoeckler at Dev Days Athens. We will pursue this as it makes a few things simpler. In particular, it is currently not easily possible to make the scheduling field single-value, but that really would be nice to have. Also, it would be good to be able to configure the allowed interval types as a field setting, so that we can add validation constraints for that.

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented
Status: Active » Needs review

OK opened a MR for this now: https://git.drupalcode.org/project/scheduling/-/merge_requests/8

This comes with quite a big refactor but things seem to work pretty much the same as before.

  • tstoeckler committed d7e194e4 on 2.x 
    feature: #3583858 Change the field into a normal field

By: tstoeckler...
tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented
Status: Needs review » Fixed

Fixed now via https://git.drupalcode.org/project/scheduling/-/merge_requests/10

Also tagged a 2.0.0-beta1 with this change.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

  • namingthings committed a72b1e37 on functional-javascript_update 
    Adapt SchedulingWidgetTest to the change into normal field (feature: #...

  • tstoeckler committed b81f8404 on functional-javascript_update authored by namingthings 
    Adapt SchedulingWidgetTest to the change into normal field (feature: #...

  • namingthings committed a72b1e37 on functional-javascript_update 
    Adapt SchedulingWidgetTest to the change into normal field (feature: #...

  • tstoeckler committed 66e6c8ad on functional-javascript_update authored by namingthings 
    Adapt SchedulingWidgetTest to the change into normal field (feature: #...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.