Bookings, backend, date -filter

This topic contains 4 replies, has 2 voices, and was last updated by  Stephen Harris 3 weeks, 1 day ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #39321

    Hi,

    I discovered that it’s no longer possible to filter bookings by date (WordPress backend panel) which has been a very useful feature.
    I have been troubleshooting and found that it is related to the WordPress core version.
    If I roll back to WordPress 5.5 it starts working normal again but after upgrade to latest version the date select list never shows up. I can still filter by event only and no errors appear.

    I´m running EO Version 3.10.4 and have tested with both 2.0.1 and 3.1.0-beta-1 for EO Pro

    Thanks!

    AK
    #39461

    Hi,

    Did you get a chance to look into this?
    I tried upgrading to EO Pro version 3.1.0 but the date -filter option does not appear.
    Still when I roll back to WordPress 5.5 the date option filter starts working again.
    Our clients use a lot of recurring events and are asking why it stopped working.

    Thanks!

    AK
    #39482

    Hi Anders, thanks for reporting this -it should be fixed in the 3.1.1 version.

    Stephen Harris
    #39552

    Thank you Stephen!

    Date filter is working fine again.

    I’m still testing v3 at my staging and there is just one thing I just wanted to check with you before I upgrade:

    When I have a browser console open while submitting a booking form and I intentionally leave out a required field or giva a wrong answer to the math question.
    This brings up the expected validation error messages for the user.
    However in the browser console there now is the following error:
    “XHR POST /wp-json/eventorg/v1/booking HTTP/2 400 Bad Request”

    When the form is filled out corrected, submission is working normal.

    Is that browser console error expected/normal here or is it a bug?

    Grateful for your insights on this before I upgrade!

    Thanks!
    Anders

    AK
    #39576

    Hi Anders,

    That’s expected behaviour. The “400 Bad Request” is the API responding that it cannot process the booking because the browser sent an invalid booking (e.g. missing required field)

    Stephen Harris
Viewing 5 posts - 1 through 5 (of 5 total)
To enable me to focus on Pro customers, only users who have a valid license for the Pro add-on may post new topics or replies in this forum. If you have a valid license, please log-in or register an account using the e-mail address you purchased the license with. If you don't you can purchase one here. Or there's always the WordPress repository forum.