|
PixelPowerCLE
|
September 22, 2024 at 3:38 pm
Just installed EE and discovered that EE has zero out of the box compatibility with AVADA which is surprising and not in line with EE competitors. In the support forum I see numerous AVADA threads for specific issues going back many years.
AVADA IS the top selling premium theme/page builder for WordPress and it would be in the best interest of EE to fully support it.
I own a marketing agency that builds websites only using AVADA and don’t want to waste my time trying to figure this out if you don’t have the documentation or intention of supporting AVADA because I can use a competitor that natively supports AVADA.
Is there documentation anywhere for your customers who use AVADA to make EE work with AVADA?
|
|
PixelPowerCLE
|
September 22, 2024 at 4:02 pm
I’ve created a custom plugin with the snippet code from https://eventespresso.com/topic/avada-theme-layout-on-events-page/
and the single event will now display.
The Ticket selector is not showing which is the same problem for the original creator of the thread.
Wordpress Read Setting is set to “Full Text”
The EE Event setting “Display Ticket Selector” is set to “Yes”
Example Event: https://nawic-cleveland.pixelpowercle.website/events/marcum-construction-summit-oct-29-2024/
|
|
Tony
|
September 23, 2024 at 8:07 am
Hi there,
The issues I’m aware of with Avada are mainly CSS fixes, with the exception of relatively recently using Layouts and MegaMenus (which is where you’re running into an issue currently).
Both of those features are running in a non-standard way, the layouts run the_content multiple times which causes the duplicated content you saw previously. MegaMenus completely replace (they call it to override) the global post to do its own processing but then doesn’t pass that overridden post object around anywhere for us to be able to know what’s happening.
The Ticket selector is not showing which is the same problem for the original creator of the thread.
The reason for this is down to the MegaMenu in use in the header.
AVADA load the page, hook in if there is a mega menu, override the global post and run a bunch of processing to build out the menu running the_content, which then triggers EE event details injection. Then they switch back to loading the main post content, but without passing the previous post to show its been overridden.
I’ll check in with our developers to see how/if we can work around that and will let you know any feedback they can provide here.
In the meantime if you set the EE events to use a navigation menu not using the mega menu that should allow the ticket selector to load.
Is there documentation anywhere for your customers who use AVADA to make EE work with AVADA?
We currently do not have any documentation to work with AVADA, I’ll open a discussion on AVADA with the team.
|
|
PixelPowerCLE
|
September 24, 2024 at 2:05 pm
“Mega Menus” have become a legacy item in the AVADA theme and are disabled by default. “Mega Menus” are now part of the AVADA library elements and I cannot identify a way to disable them. I’ve deleted and mega menu items in the AVADA library but that had no impact on the ticket selector display.
https://avada.com/documentation/how-to-use-the-mega-menu-builder/
If you know of a way to “disable” Mega Menus which is now more ambiguous, please let me know. We are trying to use this product in a current build and it is now preventing development progress because of this issue. This is a critical issue for us because we use AVADA exclusively and EE is not fully functional or supported. I’m trying to give EE a chance to work for us but we are running out of time for this use case.
|
|
Tony
|
September 24, 2024 at 2:14 pm
If you know of a way to “disable” Mega Menus which is now more ambiguous, please let me know.
So right now you have a layout using a mega menu within it for the navigation applied to all pages across the site, correct?
Create another layout (basically a duplicate of what you currently use) but set to only apply to EE events, select a navigation layout that does not use a mega menu for those pages.
Does it work then?
|
|
PixelPowerCLE
|
September 24, 2024 at 3:14 pm
I am not using Mega menus anywhere on the site.
|
|
Tony
|
September 24, 2024 at 3:29 pm
Can I take a look?
I can’t reproduce this without having a mega menu set so need to figure out what is causing this.
If so, just send temp login details over using this form:
https://eventespresso.com/send-login-details/
|
|
PixelPowerCLE
|
September 29, 2024 at 10:23 pm
Access to the website was confirmed 3 days ago and no response. I need to go live with a project and I can’t because EE doesn’t work properly. If you can’t figure out the issue I need to know so that I can get a refund and move forward with a different product.
|
|
Tony
|
September 30, 2024 at 9:12 am
Hi there,
My apologies for the delay, I’m waiting on feedback from one of our developers on this.
In the end I copied all of your layout and settings for Avada to a test site, the problem on your site happens when selecting the Blog Post Content template section for the_content.
EE injects the event details into the_content on the fly so overriding that section is forcing it not to inject event details. The only way to work around that as it stands is to not use a layout section for the_content.
I created a quick layout on your site and applied it to a single test event to confirm this worked, however, it won’t give you the level of control you are current using within AVADA to set up the post content layouts.
|
|
PixelPowerCLE
|
October 1, 2024 at 12:33 am
I just don’t understand why EE doesn’t have an AVADA content widget. AVADA has been around for almost a decade. Unfortunately, EE doesn’t not work as advertised and does not function properly with AVADA and I will refund EE.
Thanks for all your efforts Tony.
|
