Hi Laurence

Thank you for reaching out to us.

All  those information are being pulled from Amelia, so we can't change words.

We can try hiding some lines with custom CSS, but it's not recommended, because it will modify the cart and the checkout for all products, not just Amelia.

Unfortunately, we don't have hooks (action and filters) at the moment. What we have is a few JS hooks that are triggered depends on the view:

window.beforeAddToCalendarLoaded()
window.beforeBookingLoaded()
window.beforeSearchLoaded()
window.beforeSearchFiltered()
window.afterSearchFiltered()
window.beforeConfirmedBooking()
window.beforeCatalogLoaded()
window.afterSelectCatalogCategory(object_category)
window.beforeCatalogCategoryLoaded(object_category)
window.beforeCatalogServiceLoaded(object_category, object_service)
window.afterSearchActivateService(object_appointment, object_serviceActive)
window.afterSearchGoToSecondStep(object_appointment, object_serviceActive)
window.afterBookingSelectDateAndTime(object_appointment, object_serviceId, object_providerId, object_locationId)
window.afterBookingSelectService(object_appointment, object_serviceId, object_providerId, object_locationId)
window.beforeConfirmBookingLoaded(object_appointment, object_service, object_provider, object_location)
window.afterConfirmBooking(object_appointment, object_service, object_provider, object_location)

JS files are modified (minimized) in the public version of the plugin (in our development environment is accessible), but unfortunately, I can not send you our source code because that is the policy of our company.

All those files that have extension .vue are compressed and minimized in JS files that are very hard and not recommended modifying. So in order to add some other features, you can unminify the js and customize it.

There isn't a possibility in Amelia to block blacklisted users with its current features, unfortunately. There isn't an integration between Amelia and any such plugin, so we can't say if and how that will work with another plugin.

If you want you can try with some customization services, like Codeable for example, Codeable Custom Solution for Amelia plugin or Kraken  https://wpkraken.io/?tms-plugins (by following the links they would know it is our recommendation).

Hi Laurence

To be honest I am not that familiar with webhooks, so let me forward this to my colleague in Level 2 he might be able to provide you with more useful information on that matter 

We appreciate your time and patience.

Hello Laurence

You can override the default data written in the cart by modifying the "Description for WooCommerce" located in "Set MetaData and Description" in Amelia Settings/Payments, on the bottom of the page.

In order to hide "Appointment info:", please add this CSS to the page:

dt.variation-AppointmentInfo {
display: none !important;
}

Then, in the "Description for WooCommerce" add these placeholders:

%service_name%
%appointment_date_time%
Number of Vegans attending: %custom_field_11%
Number of Gluten Free attending: %custom_field_12%
Number of Vegetarians attending: %custom_field_13%

Just replace the IDs of custom fields with the IDs of your custom fields.

The "Appointment" is the name of the default product which is created in WooCommerce when you enable WooCommerce payments in Amelia. You can modify it through your dashboard/Products. So, you can change it to say whatever you want it to say. 

Here's how it looks like on my end:

"Tea" is the altered name of the product, so instead of "Appointment" it now says "Tea", while "Service 1" is the name of my service, so on your end, it would be "Afternoon Tea for 2".

No worries, Laurence, as long as it works! It's a relatively new addition to the plugin, also. In the past you weren't able to change this.

Let me know if you have any other questions or issues.

Hello again Laurence

Amelia doesn't yet have hooks and actions you could use to modify this. Since you're entering strings in the description, it will always be displayed.

I'll reach out to our developers and see if there's a way of changing this, so the info is only displayed if the custom field exists, but I can't promise anything.

Hi again Laurence

I'll forward your feedback to them, no worries.

Our development team seems to have found a way to do this, with conditional logic, but it still needs to be tested. We'll test it next week, and if it's working properly without any conflicts, we'll send it to you, and include it in our next update.

Thank you for your patience, Laurence.

I can't guarantee that it will be done next week, but we have our developers on it.

Hi again Laurence

We just released an update that includes a CSS class "am-cf-empty" for all empty fields that have no values.

All you need to do is wrap all rows in WooCommerce metaData description inside <p>...</p> tags, and add this class in Custom CSS:

.am-cf-empty {
    display: none;
}

Custom code needs to be applied to the page where the booking form is. Depending on what you're using (Gutenberg blocks, or some page builder), adding the CSS or JS can be done in a few different ways. 

If you need help with adding custom CSS to the page, please take a look at this article.

If you need help with adding custom JS to the page, please take a look at this article.

Hey Laurence

Unfortunately, the CSS is being overridden in the emails, so it's not going to work there.

The development team has been informed and they'll be working on this for our next update.

Hello Ruben

If you're referring to the conditional logic in the emails, unfortunately, something like this is not possible with the plugin yet, but I will add your vote to our developers' To-Do list, so they can work on it in the future.

Sorry for the delay, but we develop and upgrade features based on the number of customer requests. This hasn't been requested frequently, so it's not high up on our list.