Skip Navigation

[Resolved] SyntaxError: Unexpected token '

This support ticket is created 7 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Our next available supporter will start replying to tickets in about 1.82 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 1 reply, has 2 voices.

Last updated by Beda 7 years ago.

Assisted by: Beda.

Author
Posts
#590696

I have a Layout which I am unable to edit in the backend due to it's edit page not allowing me to scroll or click any of the layout related buttons.

In console I am seeing SyntaxError: Unexpected token '<'

I have checked the views and content templates within this layout and have found no unexpected < character.

I have tried creating a new view and transferring the content but with no luck - I have no problem editing the view until the first tie I refresh the page and/or save it, at which point it becomes uneducable and I cannot scroll the page.

Can you advise on what may be causing the issue and how it could be resolved?

#590788

It seems you narrowed the issue down to a View?
In this case the View eventually has some Custom JS added to the HTML inputs or even Custom JS in the JS Editor?
Can you disable it and test again?

The steps I will do if I debug this is to remove every thing from that View. Then, reinsert things steps by step to see when the issue comes back.
Then I know the culprit code and can start debugging.

If you wish I can do that on your live site, test site or on a local copy of your Install if you can send me one.
https://toolset.com/faq/provide-supporters-copy-site/

Please also make sure this issue is not caused by any other plugin or theme by temporarily disabling them.

Thank you