recurrence displayCond

[stephangrass]

Since 'recurrence overrides' only makes sense if you have selected something in 'recurrence' and 'userdefined recurrence' only if 'recurrence' is set to 'user defined', should not the fields in the TCA be displayed / swirled accordingly by displayCond?

By adding to field 'recurrence':

'onChange' => 'reload'

By adding to all 'ud_fields':

    'displayCond' => [
        'AND' => [
            'FIELD:eventtype:REQ:TRUE',
            'FIELD:recurrence:=:7'
        ],
    ]

By adding to 'recurrence_updated_behavior' and 'newsrecurrence':

    'displayCond' => [
        'AND' => [
            'FIELD:eventtype:REQ:TRUE',
            'FIELD:recurrence:>:0'
        ],
    ]

[daCyberpunk]

I'm sorry for the late answer!!!

At first point that sounds very good. But it would lead to a lot of reloads all the time what might make some user/editor much more unhappy.

But my future plan is also not to use that recurrence overwrite during save anymore. Instead I want to add a explicit button to that tab where a user/editor can call the recurrence build directly. Would be much more user friendly.

[bocianl]

So the user must every time choose "Recurrence Overrides" even if this element is not used? Eventdate recurrence is off.

[fchaussin]

I have a similar issue when I attempt to create a non reccuring event.
It ask me to set recurrence override behaviour, then if I select "do nothing", it is not saved.
Here my Event Data screenshot: