thomas83at
Forum Replies Created
-
*UPDATE*
The support send us a custom css which simply adding an padding-top above the booking form..am-cat__wrapper.am-fcil {
margin-top: 120px !important;
}
.am-cat__wrapper.am-fcis {
margin-top: 120px !important;
}So finally we need to add for every page with booking orm 240pixel empty above above the form on desktop and mobile phone, just to avoid the auto-scroll to content of amelia plugin cause massive problems with sticky header. All other pages of this project working fine without any problem with sticky header. But if a page have auto-scroll, in this case caused by amelia, you have to add a large empty space above your booking form. Amelia have no option to disable auto-scroll for booking forms which using sticky headers or for pages which placing the booking form in top section of the page and where no auto-scroll is needed. After weeks we getting css codes which was not tested for our case and was not working. After weeks stucking in this simple project with an simple sticky header we finally fall into the solution we already wrote in our initial message ticket: We have to add a large headline above the booking form or an empty space. After weeks the support also found this solution and confirmed the problem.
And no, the problem is not caused by sticky header in general.
All other pages and booking forms (from other thirdparty booking form plugins) working fine with the same sticky header. The problem root/the problem is caused by amelia auto-scroll, which is not needed in every project and will cause in every project with sticky header the same problems.We are in 2026 and talking about a sticky header problem caused by a plugin which can not handle it.
The only workaround is to add a empty space. This is not a solution, this is an desaster in ux and ix. The mobile view looking terrible, more then desktop. Who wanna have 240pixel empty space on a page in mobile view above his form? πHello Nikola,
absolute wrong feedback and your team already confirmed this negative effect of your plugin and we never get any feedback with a solution. Please share it here or in another channel. Because we still stuck in the problem.
Also your own demo have this problem. π You solved it by adding a large empty space or a large headline above every booking form! This is a messy workaround and not a clean solution. The problem itself started by your plugin. Let me explain how to trigger this problem:
Let say you are a webmater and create a website with sticky header.
1. Add a sticky header to your website.
2. Now place amelia booking into a page with sticky header.
3. Open the page “Home” or “About us”. Is the sticky header overlap any content? No!
Great. So a sticky header do not cause this problem in gneral.
4. Now open the page where you added the booking form and select a service.
In the momet when you click on a category or on a service the next page will open and amelia is doing a scroll down. The scroll down is the problem, which is caused/triggered by amelia plugin. At the moment when amelia force browser to scroll down the element like “back” and “Book now” is overlapped by sticky header. So the scroll-down effect triggered by amelia is the problem, which making it impossible to have a simple sticky header with amelia. Users who have an sticky header simply stuck in this case when using amelia booking plugin and there is no option to disable auto scroll.
Now lets see how amelia is solving this problem in their own demo:
They adding an ugly empty space above every booking form or a large headline with at least 360pixel height to avoid the scroll down effect cause cause any overlapping content. If you remove this empty space or headline, the amelia demo will have the same problem.
But:
Woud you wanna have a empty space or headline over every booking form?
Maybe not?!
If your booking form is in top section placed no scroll down effect is needed by amelia.
A plugin shoud not force users to add empty space to every booking form page or large headline. If this is not needed show us how to solve that in our website. A sticky header is nothing special or fancy. A plugin shoud work with basic requests like this. Right now the only solution is to add a large empty space above every booking form.
2. “This custom CSS has been provided to you on a different channel and we hope it will give the needed results. Please reach out to us if anything further is needed.”
I can not confirm this. Where did you send it please? No ticket with any solution regarding this case.Or share with us an quick fix with an custom css to correct the position after scroll down.
Hello Nikola,
you wrote:
“The only confirmed issue here is the service sorting behavior, which is already logged and being worked on.”Our issues/requests which are still open:
– conditional custom fields -> still not possible in 2026.
– Voucher/gift card (the most sold product in all sport studios and day spa) -> still not possible in 2026.
– Ask the customer about his birthday in booking process one time and send a birthday email based on this field value -> still not possible to send a birthday email based on date picker in booking process. We have to copy/paste that birthday value as a webmater for every client in another field one by one. Or the customer have to create a user account and add his birthday in the customer profile manual. Who is going to do this? Why not give us a option to add a birthday field to booking process and save this value into customer account for birthday email? Why complex and not make it simple? Why copy/paste or extra work for customer instead make it smart? We dont ask for a super fancy functions, this are basics.
– Showing a list of services and link the title of service and image of service -> still not possible in 2026. Very confusing UX/IX. We running a test with 900 users. 88% clicked the image and then clicked on title. Then doing a click on image twice then they understand they have to click the small button.– Services usually have a start from price. It woud be great to have a sufix or prefix for the price like: start from 100β¬ and not only showing 100β¬. Its still not possible in 2026.
– Your company working with firstname only. We see in chats and tickets only the firstname, no familyname is shown. Why you force webmaster which is using this plugint to add firstname AND familyname? In Dayspay, sport studio and many other company the webmaster/CEO only wanna show the firstname. -> this is not possible, we always have to fill the lastname also. A small point, but very frustrating to talk about minor issues like this in 2026.
– “For GDPR/terms acceptance, this can already be implemented using Custom Fields by adding a required checkbox or radio button, along with a hyperlink to your terms (for example in the field label). These fields are part of the customer information step, which appears at the end of the booking process (before payment), where user data and consent are typically collected.”
-> This is interesting. In your own booking process (checkout) its in the last step, like in woocommerce. Also other booking plugins showing the GDPR/terms acceptance checkbox above the “BOOK NOW” button and not one step before.
– For GDPR/terms acceptance like this is not possible without custom css:
(x) I accept the terms.
Without custom css only something like this is possible:
I accept the terms.
(x) Yes, i do.
– Totaly mixed sort order of all services in backend and frontend after change a small detail like price or title in one service -> Its still not solved and webmaster have to sort all services after changed one small details. A hard work which take +30 minutes every day after they changed a detail in a service. After a long time there is no patch and no official bugfix
This is a only small list of missing functions, confusing workarounds, bad UX/IX and bugs. How woud you like to work like this in a daily business with this plugin?
Please dont get me wrong. We only wanna try to speed up the improvements and the quality of the plugin. Because this are basics, or its okay for you?Hello Nikola,
finally you hvae confirmed all the problems. Lets step into each point one by one.
Birthdays / customer data: Amelia follows a structured booking flow where essential booking data is collected first, and additional customer data can be managed later. Birthdays, for example, can be added and stored through the Customer Panel, rather than being part of the booking form itself. The booking form is not designed to collect every piece of personal data upfront.The client start the booking process and adding all his personal information.
Now we can ask in a custom field about his birthday date. But we can not use it for birthday mail reminder which amelia have. Because we have to map it one by one via copy paste for every new customer. Who love to work like this? The other solution you share is: the customer need to do a extra step and login into his account after created a service and adding his birthday data into his profile extra, so we can send him a birthday email. Which client love to do this extra in a extra part after finished his order/booking process? So finally the question is: Why not making it smart and give the webmaster the option to add a birthday field to personal information tab in the booking process? smart and easy and let the webmaster decide what suits more for him. No manual work like copy and paste and no extra work for client. Like all other booking plugins.
Gift cards: This feature hasnβt been ignored, but delayed due to internal priorities. As mentioned in our previous conversations, it is on our roadmap and expected in Q3 this year, unless something unexpected comes up. Itβs something weβre actively working toward, not overlooking.That is a great news, because we are in 2026 and talking about one of the most needed service marketing material like gift cards. π
Employee names in Calendar: This was a temporary issue and has already been addressed. Instructions on how to configure the Calendar view are available in our documentation.I can not confirm the linked request in your voting board with +700 upvotes is fixed. Also your team confirmed they working on it. And most of all comments in this request wrote: we role back to 8.x version because its so important for us…
GDPR / Terms acceptance: This can already be implemented using Custom Fields (checkbox or radio button), where you can include links to your terms using standard HTML like <a href=ββ¦β>. This is also explained in our documentation: https://wpamelia.com/documentation/booking-custom-fields/
Please show me a solution that is looking like a simple legal term checkbox like this:
(x) I accept your legal terms and gdpr
Your solution is this:
I accept your legal terms and gdpr
(x)Yes
Please show me one project which using a select option under the subject line for legal term checkbox. I am a developer in the last 18 years and i never have seen something like this (option for a legal checkbox). And please show me one project in internet or in any other booking form where the user have to accept the legal terms in the middle of the booking/purchase process and not at the end. Its so frustrating to ask for basics and handle common basics different.
UI points (images, service names, sorting, etc.): These have been acknowledged through your previous tickets. Some are already being improved, while others are under consideration as part of broader UI/UX updates.Yes, and they are still open. Also the bug with sorting option is still open after +3 weeks and our clients have to arange every service from scratch after change a small detail like price or title. Who love to work like this? You? If not: Why your team can not work on major issues like this via a patching option in your plugin to fix small points with a major issue? Other plugins have a patcher section.
Hello,
we was running your plugin on 7 projects. All hat this problem.
Also in this forum we see a user 8 days before reported exactly the same problem.
in Facebook wp forum two other users report the same problem.
We have switched to the official plugin from paypal and the issue is solved.
Where we can review this plugin?
BR- This reply was modified 2 months ago by thomas83at.
My team reported another project that have this issue around 1 week. I checked the plugin and its also your plugin. We switched in this project also your plugin to the official paypal plugin and now its working fine.
I will ask the client of this project if they wanna switch the plugin or if they wanna doing debug with your. I will contact you via ticket system/email.“Nothing about how the PayPal plugin processes the shipping address request has changed. Thatβs an indication that something on your site changed.”
“Many times, this issue is caused by custom code where output is echoed to the WP Rest API request, which expects JSON. That will cause the request to fail.”
– What changed: We have updated woocommerce.
– No, we do not have any custom code.
– We disabled all other plugins.
– We switched to wordpress default theme.
– The problem is still not solved by doing this. It was solved after switched to paypal native/default plugin.
I talked to the other users who report in forum the same problem. And they also switched already the payment plugin and from that moment the problem was solved. So we also trying this – and yes, this help also in our project.
“Please provide more details like a product page url to a site where this can be replicated”
-> We can not send client projects here in public. The problem is in all products (single products).
-> Also in this forum another user report the same problem. I wrote him today if he get a solution from you.BR
I see requests in the features request board regarding this case which are 4 years old and which have +800 upvotes and users asking per month regarding a update and nothing happen. It woud be great if you plan to start working on booking basics like this. π
Hello, but in this case we talking about projects we handle with free version. Not with the paid version. Its not allowed to talk about paid projects in this forum.
We have send you many tickets – and all are unsolved regarding this issue.
I asked in another wordpress forum two other users where i saw thy using your plugin. Also they have the same problem – and always to a hard refresh in browser to fix that problem. I told them to contact you also.Hello,
also woocommerce team installed your plugin in a sandbox and it was not working in most of all browser. So major browser like firefox and chrome shoud improve their browser or you shoud improve your plugin?
We have reported this issue in the free plugin edition so often and nothing happen.
Any chance to get a soluion soon for the free edition? We wated 9 month and we see we still stuck in the same answer: Its a project specific issue… But this is absolute not correct. Its an plugin – browser issue. Its not a server or plugin caching issue, because no caching was enabled on server, no other plugin was installed and also no cloudflare cache or something like this. Just a pure sandbox by woocommerce, your plugin and a default wordpress theme.If there is no solution we have to switch back our setup to another feed plugin.
Last but not least: We already send this request very often via your contact form and also for paid subscriptions. Nothing happen, the problem is still not solved – while woocommerce test and confirmed this issue in their sandbox. And also our dev unit testing it and confirmed this issue.- This reply was modified 2 months ago by thomas83at.
Hello UroΕ‘ and thank you for your feedback.
Your feedback sounds like we requestes a very special and fancy option in your plugin. We are in 2026 and your plugin are so long on market and still can not handle price sufix and prefix like “start from”.
In germany we also have a issue with your plugin:
Nobody in germany is allowed to show “fixed” prices in grid if they price is going to change in next step, for example if you switch the qty of hours from 1 to 2.
In that case you are by legal restricted to show the price in grid like this:
“start from 100⬔. Because maybe the price can change.
Please confirm this is not possible, so we can confirm our project owner that your plugin is not good for german and europe use cases.BR
When you open a webshop or a website with product that show:
Image
title
price
What you going to click? A small button under the price? Or maybe the image or title first? Sure, you will click the title. Why your developers make it so confusing to work with your plugin? We do not talk about very fancy special requests – this are basics of every normal website with a shop or booking form. If you see a grid with image and title, you going to click on it. Amelia dont think so? What woud you say if you have to work with a plugin like this? π
Any chance to get a solution in one of your next updates?
Or we have to send a feature request and wait some years to get a CTA box linked? π