stormhill

I ran into the same issue in 5.3.4 – free version with recurring events using the mpwem_date_time date selector. May not apply to Pro version sites with custom form configurations.

Bug: Selected date not passed to order for recurring events (v5.3.4)

On recurring events using the mpwem_date_time dropdown selector, the hidden field mep_event_start_date[] never updates when the user selects a different date. It stays locked to the first available date in the dropdown — so every order records that first date regardless of what the customer actually selected.

To make things worse, even if you manually correct the hidden field value, an AJAX call fires on date change and re-injects the form HTML with the first available date hardcoded as the default, overwriting any prior correction.

You can confirm the first part in browser DevTools console:

jQuery('input[name="mep_event_start_date[]"]').val()

Change the date dropdown and run it again — the value won’t change. If you watch the Inspector, you’ll see the field briefly update (if you’ve applied a partial fix) and then blink back to the first available date as the AJAX response overwrites it.

Root cause: The mpwem_date_time select element has no JavaScript handler to copy its value to mep_event_start_date[] on change. The AJAX response that fires to reload ticket availability re-injects the hidden field with the first available date in the dropdown as the default each time, without knowing what the user had selected. This appears to be a regression introduced in the 5.2.8 datepicker rewrite.

Workaround: creating and adding the following as a mu-plugin fixed the issue for me:

<?php
/**
 * Plugin Name: MEP Start Date Hidden Field Fix
 * Description: Fixes mep_event_start_date[] hidden input not updating when user
 *              selects a date from the mpwem_date_time dropdown on the event
 *              product page. The AJAX response that fires on date change
 *              re-injects the hidden field with the first available date in the
 *              dropdown as the default, overwriting any prior fix. We store the
 *              selection and re-apply it after AJAX completes.
 * Version: 1.0.3
 */

add_action( 'wp_footer', 'mep_startdate_fix_script', 99 );

function mep_startdate_fix_script() {
    if ( is_admin() ) {
        return;
    }
    ?>
    <script type="text/javascript">
    jQuery(document).ready(function($) {

        // Store the user's selected date globally so we can re-apply it
        // after the AJAX response overwrites the hidden field.
        var mepSelectedDate = $('input[name="mep_event_start_date[]"]').val();

        // Step 1: When the dropdown changes, store the selected value.
        $(document).on('change', 'select[name="mpwem_date_time"]', function() {
            mepSelectedDate = $(this).val();
        });

        // Step 2: Watch for the AJAX response re-injecting the hidden field
        // with the first available date as the default, and immediately correct it.
        var observer = new MutationObserver(function(mutations) {
            mutations.forEach(function(mutation) {
                mutation.addedNodes.forEach(function(node) {
                    if ( node.nodeType === 1 ) {
                        var field = node.querySelector
                            ? node.querySelector('input[name="mep_event_start_date[]"]')
                            : null;
                        if ( field && mepSelectedDate ) {
                            field.value = mepSelectedDate;
                        }
                        if ( node.innerHTML &&
                             node.innerHTML.indexOf('mep_event_start_date') > -1 &&
                             mepSelectedDate ) {
                            $('input[name="mep_event_start_date[]"]').val( mepSelectedDate );
                        }
                    }
                });
            });
        });

        // Observe the booking panel container where AJAX injects HTML.
        var target = document.getElementById('mpwem_booking_panel1') ||
                     document.querySelector('.mpwem_booking_panel') ||
                     document.querySelector('#mpwem_registration') ||
                     document.querySelector('form#mpwem_registration') ||
                     document.body;

        observer.observe( target, { childList: true, subtree: true } );

        // Step 3: Also re-apply just before form submit as a final safety net.
        $(document).on('submit', 'form#mpwem_registration', function() {
            if ( mepSelectedDate ) {
                $('input[name="mep_event_start_date[]"]').val( mepSelectedDate );
            }
        });

    });
    </script>
    <?php
}

Tested on the free version of mage-eventpress 5.3.4 with recurring events using the mpwem_date_time date selector. May not apply to Pro version sites with custom form configurations.

So are you saying that the security issue mentioned by WPEngine is present in the latest security update of the plugin (1.4.1) or that the issue was solved with the latest security update?

Brilliant Solution @carasmo, THANKS!

The other issue with the new text widget is that they removed the checkbox that controlled when to add and NOT to add p tags in place of line breaks. Very Annoying. This clearly crossed the line from helping to interfering. Hopefully that will be corrected. So much of what the dev team does is flawlessly awesome so there is little cause to complain.