When you set up a date field to collect an end date in the field settings, you are asked for a default end date, with the options Same as Default date
, No default value
, Now
, and Relative
. What I miss here, is the option Same as start date
.
Same as start date
is similar to Same as Default date
, with the important difference that the latter is static; it leaves the end date at the Default date, no matter to what value the start date was changed by an editor. Same as start date
in contrast would work dynamically: It would pick up the value of the start date chosen by an editor.
In my opinion, the Same as start date
setting makes a lot of sense when you collect an end date and when an event is in the future, which is quite often the case. An example: You add an event node on first of July and choose first of October as the start date. The end date has to be by definition after the first of October. But with the end date setting Same as Default date
, it defaults to July. So you first have to adjust the end date widget to jump from July to October (or later) before you can choose the end date. In contrast, with the Same as start date
setting, the end date widget would switch to October based on the chosen start date, saving you some widget clicks.
PR by @Graham-72: https://github.com/backdrop/backdrop/pull/1923
Recent comments
nice find! the links for the most recently updated issues in the core and contrib queues are a great way to stay on top of things—especially now that the feature freeze is just around the corner...
Seeing what issues are new
A simple way — use Field Group to create a container for fields https://backdropcms.org/project/field_group and CSS Flex оr Grid to alignment. You can also create Fieldsets to...
Layout also for /node/add/ forms?
Yes. The are several ways to do this: Install Mail System and select "Testing" for delivery in admin/config/system/mailsystem Install Maillog / Mail developer...
Prevent Backdrop from sending emails