• Resolved frg

    (@frg)


    STILL NOT WORKING.

    when minified, JS and CSS return “Bad file param format”

    With FTP I had a look into the minify directory
    wp-content/w3tc/min/0fb4a/

    There are two files:

    default.include.css.id containing i:615365546;
    default.include-body.js.id containing i:2138336412;

    nothing more..

    In the last good version 0.9.1.3 there were six files:

    default.include.615365546.css 21kByte
    default.include.615365546.css.gzip 5kByte
    default.include.css.id containing 615365546
    default.include-body.591478768.js 113kByte
    default.include-body.591478768.js.gzip 45kByte
    default.include-body.js.id containing 591478768

    So the combined/gzipped versions were never produced. Hmm.

Viewing 15 replies - 16 through 30 (of 47 total)
  • @frg- I get your point, but can’t you (at least until this is fixed) just remove those files from your server?

    Thread Starter frg

    (@frg)

    @ robnalexpress

    yes – i can get a running site with no files in the minify lists, css & js not gzipped (.. or only partly – dunno why).

    but i decided for to have the listed files minified & combined and can live with css & js not gzipped.

    tried both options for me the second is faster (testet with webpagetest.com).

    Thread Starter frg

    (@frg)

    just found.

    for the technical minded (& fit in german) here seems to be the perfect fix:

    https://kenntwas.de/2011/tips/tools-allgemein/wordpress-w3total-cache-0-9-2-1-zu-laufen-bringen/

    i ll try it as soon as i have more time – dont want to break my baby ??

    Damned, I don’t catch a word from german!

    I will wait for the next update of the plugin…

    thanks everyone. I have minify on manual – but still nothing seems to have improved….

    @frg, that solution is simply fantastic! It fixed everything for me as well. There is an incredible amount of tiny, but fundamental, changes to be done… hopefully, “M. Nieberg”, the author of that excellent article, is able to write something equivalent in English and send it to the W3TC developers; some of those fixes are really crucial.

    If it helps anyone you can use the Google translate page to view it in passable English.

    See if this works.

    Thread Starter frg

    (@frg)

    @arundel69

    glad to hear that!

    I’ve created an english version of this article
    https://kenntwas.de/2011/tips/tools-allgemein/english-version-wordpress-get-w3tc-0-9-2-1-running-with-minify-and-gzip-compression/
    google translate also translates the code. The link was also send to the developers. Perhaps it helps to make things better.
    M.Nieberg

    Thread Starter frg

    (@frg)

    it works!
    it works!

    Howto correct Minify&Gzip-errors with W3Total Cache W3TC 0.9.2.1
    (based on M. Nieberg′s
    https://kenntwas.de/2011/tips/tools-allgemein/english-version-wordpress-get-w3tc-0-9-2-1-running-with-minify-and-gzip-compression/)

    *** make backups of:
    
    wp-content/plugins/w3-total-cache/lib/Minify/Minify/Controller/Base.php
        wp-content/w3tc/min/.htaccess
        root/.htaccess
    *** edit wp-content/plugins/w3-total-cache/lib/Minify/Minify/Controller/Base.php
    
    change  ,'encodeMethod' => 'zero'
    to      ,'encodeMethod' => 'gzip'   //MN: Was 'zero', set to gzip

    *** set in admin Performance->Minify->General: Rewrite URL structure ON

    *** set in admin Performance->Browser Cache->Cascading Style Sheets & JavaScript: Enable HTTP (gzip) compression ON
     (this updates to your root/.htaccess)
    *** edit wp-content/w3tc/min/.htaccess:
    (in "W3TC Minify core" part)
    
    change  RewriteRule ^w3tc_rewrite_test$ index.php?w3tc_rewrite_test=1 [L]
    to      RewriteRule ^w3tc_rewrite_test$ index.php?w3tc_rewrite_test=1 [QSA,L]
    
    add     ReWriteCond %{REQUEST_FILENAME} !^.+\.gzip$
    after   RewriteCond %{HTTP:Accept-Encoding} gzip 
    
    change  RewriteRule (.*) $1%{ENV:APPEND_EXT} [L]
    to      RewriteRule (.*) $1%{ENV:APPEND_EXT} [QSA,L]
    
    change  RewriteRule (.*) index.php?file=$1 [L]
    to      RewriteRule (.*) index.php?file=$1 [QSA,L]
    *** edit root/.htaccess:
    
    remove a lot (60?) of linefeds which W3TC put.
    
    (in "W3TC Page Cache core" part)
    change  RewriteRule ^(.*\/)?w3tc_rewrite_test$ $1?w3tc_rewrite_test=1 [L]
    to      RewriteRule ^(.*\/)?w3tc_rewrite_test$ $1?w3tc_rewrite_test=1 [QSA,L]
    
    ("BLOGSUB/" is the name of your WP subdirectory, is missing if installed in root)
    change
    RewriteRule .* "/BLOGSUB/wp-content/w3tc/pgcache/%{REQUEST_URI}/_index%{ENV:W3TC_UA}%{ENV:W3TC_REF}%{ENV:W3TC_SSL}.html%{ENV:W3TC_ENC}" [L]
    to
    RewriteRule .* "/BLOGSUB/wp-content/w3tc/pgcache/%{REQUEST_URI}/_index%{ENV:W3TC_UA}%{ENV:W3TC_REF}%{ENV:W3TC_SSL}.html%{ENV:W3TC_ENC}" [QSA,L]
    *** make both .htaccess files writeprotected by ftp:
    
    delete the write flags
    (doesnt work for me - i only get it down to 644 not 444)
    
    after i look in admin Performance, i got the two fleshy bars:
    Disk enhanced page caching is not active..auto install
    Minify is not active..auto install
    
    .. but i ignore them because my site works!
    
    minify & gzip is ok now!
    
    i know the changes will be overwritten if i change my W3TC settings again.
    Thread Starter frg

    (@frg)

    @kw2

    Vielen, vielen Dank! Super!

    This is weird. I just switched the https://www.morrispaint.com website that was working fine to automatic minify settings and left gzip enabled. No errors have occurred that I can tell. The only difference I can tell is that the morrispaint domain is in the root of the public folder and the poppameth domain is in a sub-folder as an add-on domain.

    Thread Starter frg

    (@frg)

    @sysopsavant

    but it looks NOT highly optimized 75/100 score

    https://www.webpagetest.org/result/110519_2A_MXP8/1/performance_optimization/

    also here only 75/100 score
    https://www.webpagetest.org/result/110519_8Y_MXR8/1/performance_optimization/

    are you shure minify is on & properly configured?

    It’s on but I’m not sure it’s properly configured. I haven’t been through all the new settings yet since the upgrade. Looks like the add-on domain is causing some issues there too.

    I did the fix listed by frg and likewise ignored the warning about auto installation. Everything seems faster now but webpage test is still giving me 0/100 on CSS & JS Combine and my cookie settings don’t look too good. I just don’t have the experience in those departments to figure out how to fix them or whether it is related to this issue.

Viewing 15 replies - 16 through 30 (of 47 total)
  • The topic ‘[Plugin: W3 Total Cache] 0.9.2.1 still BAD -> FTP details’ is closed to new replies.