the released version 2.9.1 has come with an improvement for added solution for conflict with Elementor pop-up, i want to understand this. from my little experience i know that elementor pop-up does not work with shortcodes. Does this improvement meant that its now compatible with Pop-Up ?
Yes, Amelia had a conflict with Elementor pop-up and we implemented some fix for this in the newest release of Amelia. So we added a shortcode for the popup - it needs to have the ID of the button that is calling the popup
so this is how one of the shortcodes should look like in the Elementor pop-up:
[ameliabooking trigger=amelia-button-id]
so if the button ID is 1 it will be:
[ameliabooking trigger=1]
So, you create a PopUp and set this shortcode for this, you will see the option Load booking form manually when you create Amelia shortcode, where you need to provide the button's ID, please look at the attachment.
When you create a button on which the PopUp will be called you set it's Button ID (that you will provide in the shortcode above afterwards), and
You need to enable the "Prevent Closing on Overlay" option in the popup settings:
If you have any further questions feel free to ask.
Hey Marija, I also have a few questions about this. I have my button id set button id and the popup opens up alright (but it does that without the id as well). And shortcode here.
I've tried variations of [ameliabooking trigger=button service=2] and others, but it won't open the calendar that should be within the popup.
Could you please tell me have you updated Amelia to 2.9.1 ? You need to have this version.
The shortcodes are not OK as I can see, they should be like [ameliabooking service=3 trigger=button] for example. Have you enabled the. option "Prevent Closing on Overlay" option in the popup settings?
There is an option to create a shortcode using Gutenberg/Classic so you can use one of these to create the shortcode and then copy/paste it to the PopUp.
If none of the above helps please open a private ticket and provide us with login credentials so we can check it out.
the released version 2.9.1 has come with an improvement for added solution for conflict with Elementor pop-up, i want to understand this. from my little experience i know that elementor pop-up does not work with shortcodes. Does this improvement meant that its now compatible with Pop-Up ?
Hello Ahmad,
Yes, Amelia had a conflict with Elementor pop-up and we implemented some fix for this in the newest release of Amelia. So we added a shortcode for the popup - it needs to have the ID of the button that is calling the popup
so this is how one of the shortcodes should look like in the Elementor pop-up:
[ameliabooking trigger=amelia-button-id]
so if the button ID is 1 it will be:
[ameliabooking trigger=1]
So, you create a PopUp and set this shortcode for this, you will see the option Load booking form manually when you create Amelia shortcode, where you need to provide the button's ID, please look at the attachment.
When you create a button on which the PopUp will be called you set it's Button ID (that you will provide in the shortcode above afterwards), and
You need to enable the "Prevent Closing on Overlay" option in the popup settings:
If you have any further questions feel free to ask.
Hey Marija, I also have a few questions about this. I have my button id set button id and the popup opens up alright (but it does that without the id as well). And shortcode here.
I've tried variations of [ameliabooking trigger=button service=2] and others, but it won't open the calendar that should be within the popup.
Hello Helgi,
Could you please tell me have you updated Amelia to 2.9.1 ? You need to have this version.
The shortcodes are not OK as I can see, they should be like [ameliabooking service=3 trigger=button] for example. Have you enabled the. option "Prevent Closing on Overlay" option in the popup settings?
There is an option to create a shortcode using Gutenberg/Classic so you can use one of these to create the shortcode and then copy/paste it to the PopUp.
If none of the above helps please open a private ticket and provide us with login credentials so we can check it out.