Title: Uncaught SyntaxError: Unexpected token ‘[‘
Last modified: January 4, 2023

---

# Uncaught SyntaxError: Unexpected token ‘[‘

 *  Resolved [newicmda](https://wordpress.org/support/users/newicmda/)
 * (@newicmda)
 * [3 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-34/)
 * On a page of our website we have several tables in a Beaver Builder Tabs module.
   
   The tab under the World Bank Categories tab should only show 5 rows and have 
   the search option visible – neither are showing, instead, all 219 rows of the
   table show at once.
 * Inspecting the element console give the following error:
   Uncaught SyntaxError:
   Unexpected token ‘[‘ arusha2023.icmda.net/:1853What does this mean and how do
   I fix it please?
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Funcaught-syntaxerror-unexpected-token-34%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [Tobias Bäthge](https://wordpress.org/support/users/tobiasbg/)
 * (@tobiasbg)
 * [3 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-34/#post-16341278)
 * Hi,
 * thanks for your post, and sorry for the trouble.
 * This is caused by an invalid “Custom Command”, on the “Edit” screen of table 
   9. Please go to that table’s “Edit” screen, find the “Custom Commands” text field
   in the “Table Features for Site Visitors” section, and remove the code `[highlight_columns
   =2]` from that field.
 * Regards,
   Tobias
 *  Thread Starter [newicmda](https://wordpress.org/support/users/newicmda/)
 * (@newicmda)
 * [3 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-34/#post-16341316)
 * Thanks for the super fast response Tobias.
 * However, there is no code in the Custom Commands field for me to remove – none
   that are visible to me anyway.
 * Though I did delete the hidden column 2 as it was not needed, but that didn’t
   seem to help either.
 *  Plugin Author [Tobias Bäthge](https://wordpress.org/support/users/tobiasbg/)
 * (@tobiasbg)
 * [3 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-34/#post-16341437)
 * Hi,
 * that would be really strange. If possible, I’d like to take a direct look at 
   this on your site. Could you therefore please get in touch via email (the address
   is on [https://tablepress.org/impressum/](https://tablepress.org/impressum/) )?
   That way, I can investigate this directly. Thanks!
 * Regards,
   Tobias
 *  Thread Starter [newicmda](https://wordpress.org/support/users/newicmda/)
 * (@newicmda)
 * [3 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-34/#post-16342065)
 * Thanks, I’ve emailed you.
 *  Plugin Author [Tobias Bäthge](https://wordpress.org/support/users/tobiasbg/)
 * (@tobiasbg)
 * [3 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-34/#post-16342206)
 * Hi,
 * thanks! I’ll reply shortly!
 * Regards,
   Tobias

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Uncaught SyntaxError: Unexpected token ‘[‘’ is closed to new replies.

 * ![](https://ps.w.org/tablepress/assets/icon.svg?rev=3192944)
 * [TablePress - Tables in WordPress made easy](https://wordpress.org/plugins/tablepress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/tablepress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/tablepress/)
 * [Active Topics](https://wordpress.org/support/plugin/tablepress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/tablepress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/tablepress/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Tobias Bäthge](https://wordpress.org/support/users/tobiasbg/)
 * Last activity: [3 years, 5 months ago](https://wordpress.org/support/topic/uncaught-syntaxerror-unexpected-token-34/#post-16342206)
 * Status: resolved