[PATCH] Allow start and end date in separate TRs
-
Having start and end date in separate TR elements currently breaks the date range support. This is due to an unnecessarily strict selector for endDate. As a result the minDate for end date is not set, and selecting a start date doesn’t update end date even. Both can result in events ending before they start.
The selector below fixes these issues.
Example HTML
<tr class="em-date-range em-date-range-start"> <td> <span class="em-recurring-text">...</span> <span class="em-event-text">...</span> </td> <td> <input class="em-date-start em-date-input-loc" type="text" /> <input class="em-date-input" type="hidden" name="event_start_date" value="" /> </td> </tr> <tr class="em-date-range em-date-range-end"> <td> <span class="em-recurring-text">...</span> <span class="em-event-text">...</span> </td> <input class="em-date-end em-date-input-loc" type="text" /> <input class="em-date-input" type="hidden" name="event_end_date" value="" /> </td> </tr>var endDate = startDate.parents('.em-date-range').find('.em-date-end').first();Improved, looser selector
var endDate = startDate.closest('.event-form-times').find('.em-date-end').first();
The topic ‘[PATCH] Allow start and end date in separate TRs’ is closed to new replies.