Title: Javascript error after plugin update
Last modified: July 21, 2018

---

# Javascript error after plugin update

 *  [AlanP57](https://wordpress.org/support/users/alanp57/)
 * (@alanp57)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/javascript-error-after-plugin-update/)
 * Our site is not working properly after updating
 * SyntaxError: missing } after try block autoptimize_69735922ab595eec1436f8d2adca9084.
   js:172:1413 note: { opened at line 111, column 3
 * This error shows up in the Autoptimize settings page.

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

 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/javascript-error-after-plugin-update/#post-10515947)
 * Morning Alan;
    Not sure I understand, so some questions: 1. what did you update?
   2. can you share your URL? 3. did you try unticking “try/catch wrapping”-option
   in AO’s JS optimization options? 4. can you post (a link to) a screenshot of 
   this error on the settings-page?
 * frank
 *  Thread Starter [AlanP57](https://wordpress.org/support/users/alanp57/)
 * (@alanp57)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/javascript-error-after-plugin-update/#post-10516580)
 * I’m not seeing the error on the settings page this morning. Here is a screen 
   shot from the from end. [https://screencast.com/t/c4PqUUD24IOA](https://screencast.com/t/c4PqUUD24IOA)
 * The update was done earlier this week. The plugin is now deactivated so that 
   sales can be processed, so no need to send a link.
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/javascript-error-after-plugin-update/#post-10516696)
 * so, more questions (some the same as not answered yet 😉 )
 * * what exactly did you update (AO has not received an update in over 4 months,
   so you probably updated something else)?
    * have you tried un-ticking the “try/
   catch wrapping”-option in Autoptimize? * have you tried keeping AO active, only
   disabling JS optimization?
 *  Thread Starter [AlanP57](https://wordpress.org/support/users/alanp57/)
 * (@alanp57)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/javascript-error-after-plugin-update/#post-10518620)
 * I was told that several plugins were updated recently and then checking the console
   pointed the error to Autoptimize and deactivating the plugin allowed the Javascript
   to function again. Yes I tried the ‘try/ catch wrapping’. there was no change.
   For now we will not use it until the vacationing webmaster returns and can look
   at it. Thank you for your help.
 *  Plugin Author [Frank Goossens](https://wordpress.org/support/users/futtta/)
 * (@futtta)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/javascript-error-after-plugin-update/#post-10518718)
 * OK, what you *could* already do is keeping AO active and just disabling JS optimization.
   Your webmaster can obviously follow up on this here to fix the JS optimization
   problem.
 * have a nice day,
    frank

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

The topic ‘Javascript error after plugin update’ is closed to new replies.

 * ![](https://ps.w.org/autoptimize/assets/icon-256X256.png?rev=2211608)
 * [Autoptimize](https://wordpress.org/plugins/autoptimize/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/autoptimize/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/autoptimize/)
 * [Active Topics](https://wordpress.org/support/plugin/autoptimize/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/autoptimize/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/autoptimize/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: [Frank Goossens](https://wordpress.org/support/users/futtta/)
 * Last activity: [7 years, 10 months ago](https://wordpress.org/support/topic/javascript-error-after-plugin-update/#post-10518718)
 * Status: not resolved