Tagged: error, javascript, masonry
-
AuthorPosts
-
March 23, 2017 at 9:02 am #765247
Hello
until the update to 4.0.3 everything was working fine. After the update yesterday it worked at first but now it seems to be broken.
Now no masonry is displayed anymore and the console in chrome says:Uncaught Error: No layout mode: packery
at o.c._mode (avia.js?ver=2:2136)
at o.c._resetLayout (avia.js?ver=2:2136)
at o.c._layout (avia.js?ver=2:2135)
at o.c.arrange (avia.js?ver=2:2135)
at o.c.layout (avia.js?ver=2:2135)
at o.m (avia.js?ver=2:2135)
at new o (avia.js?ver=2:2135)
at HTMLDivElement.<anonymous> (avia.js?ver=2:2135)
at Function.each (jquery.js?ver=1.12.4:2)
at a.fn.init.each (jquery.js?ver=1.12.4:2)I have no idea what happened overnight because i did not made changes since yesterday…
You may see this here: https://gsa.alpineo.ch/
March 23, 2017 at 9:10 am #765256Update: Found the error myself an could fix it.
But the masonry on the homepage does not show all items. There should be 6 within 3 rows. But only 3 show up.
I checked the backend several times and the config is correct.March 23, 2017 at 11:23 am #765323Hi,
Please post us your login credentials (in the “private data” field), so we can take a look at your backend.
Login credentials include:
- The URL to the login screen.
- A valid username (with full administration capabilities).
- As well as a password for that username.
- permission to deactivate plugins if necessary.
Best regards,
NikkoMarch 25, 2017 at 2:14 pm #766599Update: Found the error myself an could fix it.
I’m getting the very same error on my website. Can you please be so kind to share your method to fix it?
Thanks!
March 26, 2017 at 4:14 am #766800Hi,
@MatthiasKrebs I checked the link provided but could not see any errors. It may be a caching issue on your end please refresh the page a a few times :)
@nightjar a plugin conflict may be one of the reason for this issue.
To find which plugin is causing the conflict please follow these steps:1. Go to your plugins page > Deactivate all active Plugins
2. Update WordPress and Enfold to latest version if you have not.
3. Make sure all the plugins are updated.
4. If the problem does not persist when plugins are turned off, activate one plugin at a time and refresh until you find the plugin in conflict.We await the results of your plugin compatibility test.
Thanks for your cooperation :)
Best regards,
VinayJune 12, 2017 at 11:54 am #806822Hello,
we are also stuck on Version 4.02 because all versions since 4.03 create the following JavaScript error on our portfolio page:
avia.js?ver=2:2017 Uncaught Error: No layout mode: packery
at o.c._mode (avia.js?ver=2:2017)
at o.c._resetLayout (avia.js?ver=2:2017)
at o.c._layout (avia.js?ver=2:2016)
at o.c.arrange (avia.js?ver=2:2016)
at o.c.layout (avia.js?ver=2:2016)
at o.m (avia.js?ver=2:2016)
at new o (avia.js?ver=2:2016)
at HTMLDivElement.<anonymous> (avia.js?ver=2:2016)
at Function.each (jquery.js?ver=1.12.4:2)
at a.fn.init.each (jquery.js?ver=1.12.4:2)Any Idea what could cause the problem, the page works fine until 4.02
Greetings from Hamburg,
Ramin- This reply was modified 7 years, 6 months ago by cyquest.
June 13, 2017 at 4:54 am #807210Hi @cyquest,
Could you copy your site to a staging area and update to the latest version there so that we could have a closer look at that please?
Best regards,
RikardJune 20, 2017 at 12:43 pm #810327Hello Rikard,
thanks for your support, you will find the link to a staging-server in den private content, also including an administrator account for this installation.
Greetings,
RaminJune 20, 2017 at 8:12 pm #810628Hi Ramin,
Please put a fresh copy of avia.js in your child theme and let us know how it worked for you.
Best regards,
VictoriaJune 22, 2017 at 2:50 pm #811565Hi Victoria,
thank you for your help – this update did the trick.
I was not aware of the this old avia.js copy, because an ex-colleague did the original setup.
Kind regards,
RaminJune 23, 2017 at 4:09 am #811927Hi,
Great, glad we could help and thanks for the feedback. Please let us know if you should need any further help on the topic.
Best regards,
RikardMarch 27, 2018 at 4:53 am #933334This is happening to me too. But only when my child theme is activate.
Can you tell me where to put the avia.js file? Do I need to reference it in my child’s functions.php?
Thanks,
CJ
P.S – I’m running Enfold 4.2.6
March 27, 2018 at 5:33 am #933370Hi cjweb,
Can you give us temporary admin access to your website in the private content box below, so that we can have a closer look?
Best regards,
VictoriaMarch 27, 2018 at 5:47 am #933379Sure. I have entered them in Private Content.
CJMarch 27, 2018 at 9:01 am #933468Hi cjweb ,
Best regards,
VictoriaMarch 27, 2018 at 9:57 am #933517This reply has been marked as private.March 28, 2018 at 6:14 am #934010Hi cjweb,
I put the reply in private box, do you not see it?
Here is what it was:***wp-content/themes/enfold-child/lib/js/plugins/isotope.pkgd.min.js
This file conflict with the isotope used in Enfold masonry. This is why you get the error and masonry breaks.Best regards,
VictoriaMarch 28, 2018 at 6:23 am #934014Arrgh my bad! Sorry, I should have found that.
Thanks,
CJMarch 28, 2018 at 12:12 pm #934190Hi,
I’m unable to view your site as the password do not to work.
Please do let us know if you need any further help with the issue or you got it sorted?Best regards,
VinayMarch 28, 2018 at 12:30 pm #934212It is sorted thanks Vinay.
CJ
March 28, 2018 at 9:25 pm #934516Hi,
Glad we could help!
Please take a moment to review our theme and show your support https://themeforest.net/downloads
To know more about enfold features please check – http://kriesi.at/documentation/enfold/
Thank you for using Enfold :)Best regards,
Basilis -
AuthorPosts
- The topic ‘Masonry not working // JavaScript error’ is closed to new replies.