JS Errors and alignment issues
Recently an odd issue is now happening. Ever since I migrated to a fresh WP install, one page is tossing up JS errors and the column alignment isn’t right.
This is the test page I setup: http://londoncapital.biz/test-affiliate-program/
It uses the default template and there is nothing there but:
Note that they are all exactly one line down from the previous.
In my JS Error plugin, I am seeing the following:
“Uncaught TypeError: Object [object Object] has no method ‘imgr’”
And it points to the test page I just created.
I need to get this site back and professional looking :)
Regarding the JS error, can you post a link to the page with errors? I’m not seeing any errors on the front end (in the browser console).
As for the space in the columns, when you switch to text view (in the editor) is there any white-space? I’m wondering if another plugin has invoked wpautop.
Can you try creating a Custom Field named “wpautop” with a value of “false” (no quotes) on the above page?
Thanks for the quick reply.
Ok, first, I’ve attached a screenshot of the JS Error log plugin and the message it’s giving me.
This is the original page with the problem
I’m seeing messages using Chrome Element Inspector on this page.
I try to do as much work as possible in the text editor only.
As for white spaces, as mentioned, how you see the quoted code is exactly how it is on the text page. no spaces.
Well, that custom field seemed to have done the trick.
As far as JS stuff goes, not sure what else you might need from me. I had a nice accordion function setup but it stopped working, so got another one. It works but not as smooth. I’m going way out on a limb that because these issues all hapened around the same time, there may be a JS issue somewhere?? Purely a guess on my part though.
I’m not sure what the JS Error plugin does. Perhaps a developer tool for checking backend compatibility?
The JS errors you’re seeing are called on the frontend and will throw an error if they aren’t enqueued properly.I wouldn’t rely on that for debugging. As far as I can see on the link you posted, there are no JS errors thrown. If you can clone the page and add the code that reproduces the error, I’ll be glad to look into it.