• Resolved heman321

    (@heman321)


    Hi,

    I found this: Error 500 when activating JS minify from latest update | www.ads-software.com

    Which exactly describes my problem. If you enabled JS minification and watch the console, you get an HTTP 500 error on the .js file.

    I found that if I change (now) line 210 or JSMin.php to:

    if ($this->a === “‘” || $this->a === ‘”‘) { // string literal

    It resolves the issue. But this issue was reported nearly two years ago, shouldn’t there be a fix in the product for this by now?

    I am always worried about leaving hacked .php files on live systems, so I would like a proper fix before I push this on to live really.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @heman321

    Thank you for reaching out and I am happy to assist you with this.
    We were investigating this issue and we were unable to replicate it on any of our instances.
    So this is the only fix for now. Can you please share your website URL, and let me know what is the caching method you are using and also the JS minifier?

    Thanks!

    Thread Starter heman321

    (@heman321)

    I am afraid this is one of our development sites, so it isn’t available outside of our office. I am a software dev. though, so I hope I can be helpful in diagnosing the issue for you.

    This is a Windows server, so the caching is just Disk\Disk Advanced.

    I assume the PHP that minifies the JS is failing, so when the browser tries to fetch it, the HTTP 500 is because the PHP is failing.

    If I try and enable the minify debug option I get “It appears Minify?URL?rewriting is not working. Please verify that the server configuration allows .htaccess” but as I am running on Windows there is no .htaccess file (or at least, not one that does anything) and it has not created and IIS rewrite rules in the web.config.

    Could we just log $this->a somewhere and see what it is working on?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @heman321

    Thank you for your feedback.

    If you have any information that may help us with this, you can use a ticket in the GitHub created for this specific problem.
    You can comment there and log any additional information that may help solve the problem!

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘HTTP 500 on .js files after new install’ is closed to new replies.