Uncaught SyntaxError: Unexpected end of input

  • Hi,

    I am getting an “Uncaught SyntaxError: Unexpected end of input” on all my sites using the plugin since the latest update. I am up to date on both WP and the plugin.

    This is a significant issue as Google is now disapproving Google ads for sites displaying this error. I have dozens of sites getting this error and all of them were disapproved for ads today. They are saying that the websites are non-functional although it loads with no problem on all browsers and Webmaster tools doesn’t indicate any issues.

    Any chance of getting a solution for this rather quickly?

    Thanks,
    Pat

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter wlpdrpat

    (@wlpdrpat)

    FYI – in reviewing other similar threads you suggested: “disable try-catch wrapping in AO”. I have tried this but when I save changes the try-catch wrapping option continues to be selected (this could be a bug). I am going to try to change it in the db and see if that fixes the issue.

    • This reply was modified 6 years, 4 months ago by wlpdrpat. Reason: add new details
    Plugin Author Optimizing Matters

    (@optimizingmatters)

    I have tried this but when I save changes the try-catch wrapping option continues to be selected (this could be a bug).

    could be stale db/ object caching?

    I’m seeing this error;

    SyntaxError: missing } after try block autoptimize_a6830038d925e2b97b1d8a590c4524cb.js:66:1413
    note: { opened at line 57, column 3

    so very likely to be linked to try/catch usage indeed.

    frank

    Thread Starter wlpdrpat

    (@wlpdrpat)

    Hey Frank,

    I don’t have db object caching enabled. Any other thoughts on how I can disable try-catch wrapping? I’m looking though the code at the moment but haven’t stumbled upon it yet. If you could point me in the right direction it would be helpful.

    Thanks,
    Pat

    Thread Starter wlpdrpat

    (@wlpdrpat)

    Hi Frank,

    I was able to disable try-catch wrapping via Edit Site Settings and that resolved the issue.

    I’m not sure why the options on the plugin are not saving. I know they were saving before I updated to the latest version (last week).

    I tried disable other plugins one by one to no avail. I also tried using the default theme.

    I will create a fresh install with no plugins and default theme and see if it is working, however, at this point I am pretty certain you have a bug related to saving settings with your latest version. BTW – I am not having problems saving settings on any other plugins or the theme – I checked 5 plugins and 2 themes.

    I will let you know what I find.

    Pat

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    Weird; no issues saving here, 2.4.1 is running successfully on _a lot_ of sites and there were no changes in how settings are saved the 2.4 branch … Do keep me posted!

    Thread Starter wlpdrpat

    (@wlpdrpat)

    Hi Frank,

    I tested it on a fresh install but with WP configured the same (multisite activated). No other plugins activated and using default theme. Checkbox options on the options page do not save but text options do save.

    I test a couple dozen other plugins and none of them are having an issue saving checkbox options.

    I looked through your code and can’t see anything jumping out at me. For the moment I’ll assume it is a multisite issue. I’m going to test a few tweaks to your code to see if I can get it working and I will let you know.

    Pat

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    bizarre, you’ve gotten me me somewhat frustrated now ??

    some questions:
    * any JS errors on the browser console?
    * anything in the php errorlog?
    * does the problem manifest on both the main site and on the child sites of your multisite?
    * does the problem go away when disabling multisite?
    * have you tried if downgrading AO to 2.3.4 fixes the problem?

    frank

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Uncaught SyntaxError: Unexpected end of input’ is closed to new replies.