-
Posted in : Efor
-
Hello,
Am using Amelia booking app and the developers tell me this theme is causing some conflicts when you try to book an appointment.Specifically some fields in the booking app are being set to “hidden” by the theme, and we have applied css like this to resolve.
.site-content form input[type=submit], .site-content form input[type=button], .site-content form button {
visibility: visible !important;
}I thought i would inform so that compatibility could be improved in the theme code.
ThanksHi,
Thanks for the feedback. I will also inform our developers.
ThanksIs this fixed? I am about to purchase the Ameila plugin, and I don’t want any conflicts. If it’s not fixed, how can I fix it?
Hi,
I will forward this topic to our developer and I will keep you updated.
ThanksI was able to add the additional CSS to my site, and it did fix the conflict.
Hi Serkan!
When I insert the “booknetic plugin” shortcode witin the “Action button” of the Jet elements or the elementor price tables it doesn’t work.
Below I write you down my wordpress login.
Thank you so much for your help!
Actually I’ve also tried with the call to actions buttons of my home page and it doesn’t work either.
Hi Artur,
To test whether the problem is related to our theme, I activated the default wordpress theme instead of our efor theme. However, the problem with the plugin still persists. This is a problem between the plugin and elementor. So you need to contact the plugin author.
ThanksHi Serkan!
First of all, thank you so much for your help!
When you did the test activating the default wordpress theme, something went wrong.
Because now, my home page has several errors on mobile (chrome) and desktop (firefox and opera):
– The logo, legal pages and copyright text don’t show up
– The H2 are differentOn desktop through Chrome it looks good.
Hi, When you switch to default wordpress, of course you cannot get the exact same image due to our plugins. I switched to default wordpress just to see if the problem is with us. But when I saw the same problem, I realized that the problem was not caused by us. That’s why I directed you to the other plugin author.
Thanks for your understanding.
You must be logged in and have valid license to reply to this topic.