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
What I typically do is truncate the flood table. This will remove everything, but since this happens just once in a while, it doesn't create issues. You could also increase the number of...
Flood Unblock analogue
After installing you choose 'structure' - 'layouts' from the admin menubar and select the new layout for f.x. 'default layout' by clicking on the template you want to change thereby getting to '...
Creating Footer columns
@herb - Perhaps I wasn't clear. The function is there in Backdrop but the code to handle the problem of this specific case is not. Specifically, the Drupal code for the function includes...
imagecolorsforindex(): Argument #2 ($color) is out of range