Archived topic
[3.1.0-alpha.1] Customizer console error: Uncaught TypeError line: 91
12 replies · Started by Elham on September 9, 2021
Wen using dropdowns while the container alignment is set to "text", the console will give an Uncaught TypeError.
Theme version:
GeneratePress: 3.1.0-alpha.1
Active plugins:
GP-Premium: 2.1.0-alpha.1
GenerateBlocks: 1.4.0-alpha.1
GenerateBlocks Pro: 1.1.0-alpha.1
Hi there,
Sorry what do you mean by "when using dropdown"?
I couldn't replicate the issue:
https://www.screencast.com/t/4LEWyCdNqJ
Can you let me know what I'm missing here?
Thanks :)
Hi,
Of course, after some further testing I found out that it gives the error sporadically regardless if "Container Alignment" is set to "Text" or "Boxes".
When you change any dropdown option. For instance the "Content Layout" option it sporadically gives the error. https://snipboard.io/DAqRMo.jpg
Strange. Still unable to replicate it:
https://www.screencast.com/t/lwkRISW6
Are all plugins except GP Premium disabled in your environment?
I'm seeing a Widget Customizer message which isn't coming from GP.
Let me know :)
here is a video which shows it happen. Hopefully this can help. It does it on any dropdown in the Customizer not only the one shown.
That's so strange. I still can't replicate it as seen here:
https://www.screencast.com/t/iQQgp4Aq
What happens if you disable GP premium?
With GP premium disabled it's gone. But the error was already in the GP premium code.
gp-premium/spacing/functions/customizer/js/customizer.js:91
Weird. My screen capture was taken with GP Premium and only the Spacing module activated.
Can you give that a shot as well?
We are getting closer I think :)
Okay this is getting weird. I've disabled all the modules and enabled only spacing and now it's gone. I've also tried again with other modules active and it doesn't give me the error anymore.
That is super strange indeed.
Can you play around some more and let me know if it happens again?
I'll do the same on my end :)
Sure thing.
Thank you :)
It seems like a anomaly. I've added some console logs into the specific file. One before the variable is set and one inside the if statement that requires the variable. And both log correctly without any problem.
Also tried with a complete fresh install and no issues there. So I don't know if this was GP or just WP giving an anomaly.