Support » Plugin: Autoptimize » YUI Compression Depreciation

  • I use YUI compression, because, at least on my servers, it is about twice as fast, compressed files are slightly smaller, and unlike with the PHP alternatives, properly written CSS5 always still validates and properly written JS code always still runs without errors. I have a strong general dislike for Java, but in this particular application, YUI compression has worked significantly better for me than the PHP code.

    I am not posting this to argue with your decision to remove it from future versions. I use a forked customized version of Autoptimize to meet unique needs and can leave it in my private version. I am merely wondering whether YUI compression is going to be removed due to Java security-vulnerably concerns, because it isn’t being widely used by plugin users, because you have found an operational problem, or for some other reason.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Frank Goossens


    Afternoon Admintiger;
    It’s not a question of java security-concerns, but just me trying to focus on what I consider core functionality and that I feel comfortable providing support for (i.e. do I know how it works and how it is coded).

    Hope this clarifies,

    Ok, that’s reasonable.

    If you want to learn more about it there is considerable information here Even though most Autoptimize users probably haven’t understood its advantages or exactly how to enable it, the YUI Compressor is actually very easy to install and use with Autoptimize, especially under Linux. It is equally easy to install and works just as well under Windows, but a few simple modifications are needed to Autoptimize to make it compatible with the YUI Compressor under Windows.

    Some WordPress plugins that fail using the PHP compression code in Autoptimize run fine using the external YUI Compressor.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘YUI Compression Depreciation’ is closed to new replies.