1.5.3 -> 2.0.1 upgrade changed JS processing, many console errors

  • Resolved Immánuel Fodor

    (@immanuelfactor)


    7 years, 6 months ago

    Dear Raul,
    I don’t know what exactly changed in the JS processing between 1.5.3 and 2.0.1 but after upgrading, the generated JS fails with many browser console errors.
    I clicked upgrade on the plugin then purged the cache, and instantly ended up with broken JS. The 1.5.3 version worked completely fine before, so I’m sorry for losing functionality.
    I tried various settings changes if I can eliminate the problem via the admin panel but nothing helped. I have a couple JS files which are dependent on loading order, maybe the plugin changed the queue of how these are included?
    If you need my site for reference, here it is, well running on v1.5.3:
    https://immanuel60.hu/
    Fortunately, I updated on localhost first to test the changes, so the production is intact.
    Please take a look into the JS processing, I hope you can find something. Maybe a new option for “legacy” processing or something else can help me/us.
    I must tell you that your plugin was the first that worked out of the box for me, I even dropped Autoptimize in favor of it ??
    Cheers,
    Immánuel

    • This topic was modified 7 years, 6 months ago by Immánuel Fodor. Reason: Autoptimize name mispelled
    • This topic was modified 7 years, 6 months ago by Immánuel Fodor. Reason: typo fix
Viewing 2 replies - 16 through 17 (of 17 total)
  • Thread Starter Immánuel Fodor

    (@immanuelfactor)

    Yes, I was lucky now as it contained English texts only. I posted it here only as a reference of what I did to solve my problem, it may help others.

    If there would be a way to query PHP Minify why it returned an empty string eg. failed with wrong encoding, that could save us from a lot of trouble, you could use it for notification in the logs. Or if it returns empty for not empty input, then use this for indicating the encoding trouble. However, the ultimate solution is sanitizing the input before passing it to PHP Minify, then it can’t return empty.

    I’ll definitely test any new solution if you push the 2.0.3 once! ??

    Thread Starter Immánuel Fodor

    (@immanuelfactor)

    2.0.5 works like a boss on Windows even with messed-up encoding. Bravo! ??

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘1.5.3 -> 2.0.1 upgrade changed JS processing, many console errors’ is closed to new replies.