Elastic Grid doesn’t work with Avada Theme

Dear ibenjo,

Thanks for reaching out us. Seems that the theme added to your website influence on plugin’s CSS styles.
For checking that could you, please, try to change your theme to a default WordPress theme for a few seconds only in order to check if the issue exists using another theme or not?

We will wait for your observations.

Thank

This case is marked as solved. Can you please give the sollution? I’ve got the same problem.

Kind regards

Dear remcla,

Thank you for contacting us,

Can you, please, provide us with your website link to check the issue first?

We will be happy to check everything and assist you.

Regards,

Hi Support,

The website is still in development and not reachable from outside. Only if you edit your host file.

At this moment I disabled the Elastic grid column because it messes up my other layout (Justified) on my page.

Setup:
2 columns on 1 page
– 1 Justfied
– 1 Elastic grid

When both enabled, only Justified is visible but totaly messed up.
When only Justified enabled, everything is fine
When only Elastic grid enabled, nothing is shown

I can provide you with the Hosts info if you want.

Kind regards,
Remco

Dear remcla,

Let us first try to duplicate the same issue at our end. ??
Could you, please, mention the theme you are currently running?

Thanks

Hi Support,

Like in the title of this article… Avada (5.2.2)

Kind Regards,
Remco

Dear Remco,

Thanks ??
We will test that from our side and will inform you about the results.

Thanks

Hi Support,

I did some debuging myself and came across this error in Chrome when I select the Elastic Grid:

avada-portfolio.js?ver=1:1 Uncaught TypeError: Modernizr.mq is not a function
at HTMLDocument.<anonymous> (avada-portfolio.js?ver=1:1)
at i (jquery.js?ver=1.12.4:2)
at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4:2)
at Function.ready (jquery.js?ver=1.12.4:2)
at HTMLDocument.K (jquery.js?ver=1.12.4:2)
avada-header.js?ver=5.2.2:1 Uncaught TypeError: Modernizr.mq is not a function
at avada-header.js?ver=5.2.2:1
at dispatch (jquery.js?ver=1.12.4:3)
at r.handle (jquery.js?ver=1.12.4:3)

Maybe it can help you to find a solution.

Regards,
Remco

Dear Remco,

Thank you very much for your observations. We really appreciate your attitude and attention.
Per your and our investigations it came out that the problem is in the modernizr.custom.js file which exists in our plugin. The plugin works properly on WordPress default themes but the conflict appears in Avada probably because of the file in the theme, which has the same name or functions in it.
We are begging your pardon but the issue could not be currently fixed at our end.
It needs deeper investigation and resources for finding the root of the problem out and fixing it.

We will definitely include this fix in our upcoming update.
We are begging your pardon again for the inconveniences you have faced.

Thanks

Hi Support,

I’ve got a pro version of the Gallery. Is it possible that I have to update? In the FAQ I’ve read that I have to send an e-mail to get a new version.

Maybe the problems exist because of the version (I use version 10)

Regards,
Remco

I received an update, but that didn’t solve the issue.

Do you have a timeframe about the upcoming update? In other words: Can this be fixed in a short time? I must deliver the website in a few days. If the fix takes a couple more weeks or months, I’m going to use a other option besides the Elastic Grid. Unfortuanaly this is the option my client choose….

Thnx for your help. I hope the update will come soon.

Kind Regards,
Remco

With the update there is a new feature in Gallery: Album. This also doesn’t work in combination with Avada. Just the same Modernizr error.

I tried to rebuild the modernizr.mq, but that gave no solution. Now i’m stuck. Website is almost done, I don’t have the time to build with another theme…

Isn’t there a workarround for the timebeing? Does Portfolio also work with moderizr.mq?

Regards,
Remco

• This reply was modified 7 years, 3 months ago by remcla.

Dear remcla,

We are really sorry but the issue cannot be fixed currently on our end.
However, we will try to detect everything as soon as possible and include the fix in the update.

Thanks