Tagged: avada theme plugin conflict
March 20, 2017 at 4:26 am #128504
It appears the Inbound Pro plugin is causing a conflict with the Avada theme.
This happened after updating both Inbound Pro and Avada, so not quite sure which update is the culprit here.
This theme come with its own Fusion Builder plugin which allows shortcodes to be used everywhere on site.
With Inbound Pro deactivated, all works as expected. With Inbound Pro activated, only the CTAs show, but not the shortcode content that is supposed to be put out by the shortcodes, even though their html is there when checking the page code.
At first I thought it wast the “enable fast ajax” option that blocked all other ajax plugins so that the CTAs can be rendered. After turning that off, it didn’t help though.
I think the Fusion Builder plugin also uses ajax to retrieve the content that is requested by shortcodes but am not sure how it works really…
Would you be able to have a look please?
Kind regardsMarch 20, 2017 at 4:32 am #128510This reply has been marked as private.March 20, 2017 at 12:23 pm #128538
It seems there’s a conflict with the theme’s modernizer script. I’m not able perform a conflict fix at the moment. Will you see what you can do? Maybe the other developer will be responsive?March 21, 2017 at 4:25 am #128587
Thanks for your quick reply, Hudson.
I created a ticket with Avada support, will keep you posted!March 22, 2017 at 1:43 am #128626
Bad news I’m afraid, Avada support came back with the following:
It does appear to be a plugin incompatibility with the theme. As theme developers, we do try to make the theme as flexible as possible, but it quite difficult to make it compatible with all the plugins in the wp repository.I apologise to make you go to and forth between the theme and plugin authors, but at the moment I would request you to please contact the plugin authors and check if anything can be done at their end. I will pass this on to my developers too and let them know to consider the plugin compatibility for a future update
So again, I have to ask if you would be able to look into this?
I can provide you with the necessary login credentials if you like.
Kind regardsMarch 22, 2017 at 1:58 am #128629This reply has been marked as private.March 22, 2017 at 11:29 am #128662This reply has been marked as private.March 25, 2017 at 1:44 pm #128703
Thank you for your information.
The Avada support team has agreed to look into the issue further and is asking for some help from your side:
My devs have checked the setup and the issue is that the plugin is enqueuing it version of modernizr
They have renamed tried to rename it for now, but they have an automated setup which prevents this.
To dequeue this we would have to comb through the plugin’s code which would require quite some time. I do apologise but at this moment the only current option remain to contact the plugin authors
I would greatly appreciate it if you would be able to share your expertise about your own code with them and point them in the right direction. I will be happy to continue to be the middleman so as to solve this issue for all parties involved. Meanwhile, the abovementioned login credentials are still valid.
Looking forward to hearing from you and have a nice weekend.
Kind regardsMarch 25, 2017 at 2:33 pm #128704
Hi I’d love to work with the Avada developers and collaborate on a solution. I’ll include my email address below.March 25, 2017 at 2:33 pm #128705This reply has been marked as private.March 26, 2017 at 6:22 am #128707
That’s great to hear, I have passed on the information and asked how they wish to proceed.
Will keep you updated!
Thanks for your willingness to help out, I am very grateful.
Kind regardsMarch 29, 2017 at 6:10 am #128795
Hi again Hudson,
I’m not sure whether Avada developers have been in contact with you yet but here’s their latest message to me:
I just checked the staging site and currently it does work fine. I see the Inbound plugin active and also Avada on latest version.
Did anything change?
Checking the installation shows that the issue indeed seems to be magically solved. This as opposed to a backup I made before developers went in to check, this backup is still showing the issue. So, some action by someone must have solved it, since the backup still doesn’t function properly.
Just wanted to ask if you had perhaps logged in meanwhile and performed any actions?
Kind regards, keep you posted.
You must be logged in to reply to this topic.