Hey there, Awesome Customers!

Just a heads up: We'll be taking a breather to celebrate International Workers' Day (May 1st and 2nd - Wednesday and Thursday) and Orthodox Easter from Good Friday (May 3rd) through Easter Monday (May 6th). So, from May 1st to May 6th, our team will be off enjoying some well-deserved downtime.

During this time, our customer support will be running on a smaller crew, but don't worry! We'll still be around to help with any urgent matters, though it might take us a bit longer than usual to get back to you.

We'll be back in action at full throttle on May 7th (Tuesday), ready to tackle your questions and requests with gusto!

In the meantime, you can explore our documentation for Amelia and wpDataTables. You'll find loads of helpful resources, including articles and handy video tutorials on YouTube (Amelia's YouTube Channel and wpDataTables' YouTube Channel). These gems might just have the answers you're looking for while we're kicking back.

Thanks a bunch for your understanding and support!

Catch you on the flip side!

Warm regards,

TMS

Okay
  Public Ticket #3531962
Shortcode filters resetting
Closed

Comments

  • Joern started the conversation

    We’re using the step by step booking form shortcode [ameliastepbooking] in the standard block editor with custom parameters to filter location and staff.

    On every new page load in the block editor, the saved parameters are reset / disappearing. If we then save the page, the parameters are deleted on the front end form. This means whenever we make a change on the page, we need to remember to manually reselect all of the Amelia shortcode parameters, or else the form will reset to the default booking form. This happens for all dropdown parameters, but not for "trigger type" and trigger to load form manually parameters, which still get populated fine.

    We are using 7.1, but it also happend on 7.0. Happens on multiple sites and on different servers.

    The old shortcode works fine. [ameliabooking] loads with the saved parameters as expected.

    There are no console errors.

    It appears to be a conflict with Genesis Blocks, but it arose only since updating Amelia. Rolling back Genesis Blocks has no effect: Something in the new Amelia updates caused this.

  •  1,177
    Uroš replied

    Hello Joern,

    Thank you for reaching out to us.

    Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

    We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

    You can write credentials here just check PRIVATE Reply so nobody can see them except us.


    Kind Regards, 

    Uros Jovanovic
    [email protected]

    Rate my support

    wpDataTables: FAQ | Facebook | Twitter | InstagramFront-end and back-end demo | Docs

    Amelia: FAQ | Facebook | Twitter | InstagramAmelia demo sites | Docs | Discord Community

    You can try wpDataTables add-ons before purchasing on these sandbox sites:

    Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables