I added the shortcodes for reservations with the amélia plugin on my website. however it is not displayed correctly. The visual cut and we can't see it well? I would like to know how to correct this?
In that case, 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.
Hey Vincent, sorry for all the back-and-forth, but WordPress is an extremely dynamic environment, and until all other issues that could impact our plugin are resolved, we cannot get to the bottom of the issue.
Mixed content occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS. Even though this didn't resolve the issue with Amelia, resolving it most likely spared you some time with some future issues that didn't come up yet. Mixed content is tolerated up to an extent, but it is only a matter of time before the content of the page is blocked by the CORS policy, so this was not in vain. Our team will work on direct integration with the DIVI builder, but at the moment there are conflicts with it. Since the builder is extremely popular, they got lazy, and they don't really care about any other plugins or themes you may have, so in their styles, they're writing global classes like:
em
form
h1
img
input
label
li
object
span
textarea
vide
ul
And so on. Doing this, they are overwriting any CSS containing variations of those styles. Just to show you what I mean, here's what's impacting the form:
And that's just the first part. When we turn off all these checkboxes you see checked-off, the select-box is still coming out wrong, so we have to inspect that element, and disable DIVI's styles for .input:
I don't know how our developers will address this when they start working on an integration with DIVI, but it will be a major task since they have to overcome all this lazy coding to avoid conflicts with global selectors. If you were to inspect our styles, you'd see that even though we have similar classes, they are almost always preceded by "am-" exactly so it doesn't conflict with other plugins or themes.
At the moment, the only workaround for this would be to either create a complex custom CSS that would override their styles or disable the builder on pages where Amelia is included.
This conflict cannot be resolved easily, nor fast, so unfortunately until the integration with DIVI is released, there's not much we can do.
I added the shortcodes for reservations with the amélia plugin on my website. however it is not displayed correctly. The visual cut and we can't see it well? I would like to know how to correct this?
Hi Vincent,
thank you for reaching out to us!
It does look very broken, the layout can look like this in case that the customization was not reset, or there is a theme conflict.
Can you please go to Amelia > Customization > Reset it, set your color scheme, and Save?
Please let me know if this worked.
Hi Ivana
no, it didn't work!
Hi Vincent,
thank you for letting me know
In that case, 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.
Hi Ivana,
I have fixed this and the issue is still there. Please advise.
Thanks,
Hi Vincent,
thank you for letting me know!
In that case, I have forwarded the issue to the developers, so that they can see where the cause is; I will contact you with their conclusion
Great! Thank you. How long do you think it'll take before I get an answer?
Hi Vincent,
we found it.
Looks like there is a conflict with Divi Builder, please try turning it off on that page only, and let me know if it works.
hi Ivana,
Look. At first you had me fix something totally unrelated, now you tell me an engineer had to get on to tell me there's a conflit with my builder.
I could have told you everything up so far. Turning off my website's builder is obviously not an option.
Can you guys work on a fix or are we divi users just going to be ignored?
Thanks.
Hey Vincent, sorry for all the back-and-forth, but WordPress is an extremely dynamic environment, and until all other issues that could impact our plugin are resolved, we cannot get to the bottom of the issue.
Mixed content occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.
Even though this didn't resolve the issue with Amelia, resolving it most likely spared you some time with some future issues that didn't come up yet. Mixed content is tolerated up to an extent, but it is only a matter of time before the content of the page is blocked by the CORS policy, so this was not in vain.
Our team will work on direct integration with the DIVI builder, but at the moment there are conflicts with it. Since the builder is extremely popular, they got lazy, and they don't really care about any other plugins or themes you may have, so in their styles, they're writing global classes like:
And so on. Doing this, they are overwriting any CSS containing variations of those styles. Just to show you what I mean, here's what's impacting the form:
And that's just the first part. When we turn off all these checkboxes you see checked-off, the select-box is still coming out wrong, so we have to inspect that element, and disable DIVI's styles for .input:
I don't know how our developers will address this when they start working on an integration with DIVI, but it will be a major task since they have to overcome all this lazy coding to avoid conflicts with global selectors. If you were to inspect our styles, you'd see that even though we have similar classes, they are almost always preceded by "am-" exactly so it doesn't conflict with other plugins or themes.
At the moment, the only workaround for this would be to either create a complex custom CSS that would override their styles or disable the builder on pages where Amelia is included.
This conflict cannot be resolved easily, nor fast, so unfortunately until the integration with DIVI is released, there's not much we can do.