• Resolved nubic

    (@nubic)


    try to use eaccelerator, disk and memcashed too, but its not work.
    debug:

    Engine: eaccelerator
    Total queries: 131
    Cached queries: 0
    Total query time: 1.508

    memcashed too
    in any pages

    <!– W3 Total Cache: Page cache debug info:
    Engine: eaccelerator/disc/memcached
    Key: w3tc_2336b9214d1216baf4a00089ce5fec5d_page_6666cd76f96956469e7be39d750cc7d9
    Caching: disabled (but its enabled)
    Reject reason: cookie is rejected
    Status: not cached
    Creation Time: 4.109s

    another blog at the same server is ok

    <!– W3 Total Cache: Db cache debug info:
    Engine: eaccelerator
    Total queries: 49
    Cached queries: 34
    Total query time: 0.114

    except page (i thiink becose whithout fansy urls)

    <!– W3 Total Cache: Page cache debug info:
    Engine: eaccelerator
    Key: w3tc_4a96fb9e157d43aac580f23157b1a17f_page_6666cd76f96956469e7be39d750cc7d9_gzip
    Caching: enabled
    Status: not cached
    Creation Time: 0.665s

Viewing 9 replies - 1 through 9 (of 9 total)
  • <!– W3 Total Cache: Page cache debug info:
    Engine: eaccelerator/disc/memcached
    Key: w3tc_2336b9214d1216baf4a00089ce5fec5d_page_6666cd76f96956469e7be39d750cc7d9
    Caching: disabled (but its enabled)
    Reject reason: cookie is rejected
    Status: not cached
    Creation Time: 4.109s

    Log out of WordPress and clear your cookies and try again or test from another browser you don’t normally use. It usually won’t cache for logged in users.

    Thread Starter nubic

    (@nubic)

    i logged off and used another browser

    sometimes its enabled but anyway not cached and page creating 4-7 sec

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    If the execution time is the same when W3TC is disabled then the issue is that you were logged in when checking debug mode.

    Anyway, purge browser cookies, empty browser cache and check again (when not logged in).

    Thread Starter nubic

    (@nubic)

    my server is death, after reinstal OS i install eaccelerator again/ and it works
    but in the options page of plugin this mettod is no active. i dont know why and what to do

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    Versions after 0.9.5.3 of eaccelerator do not allow “user caching” which is how W3TC can use the cache. If you have this version and it still doesn’t work, there’s an issue with the installation or configuration of eaccelerator.

    Thread Starter nubic

    (@nubic)

    Version 0.9.6

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    Ok, so what I said above is true.

    Thread Starter nubic

    (@nubic)

    but i dont wont use disc caching
    and i install memcached but
    for pages it works and for database is not

    Database caching is not working properly. Memcached server(s): localhost:3306 may not running or not responding. This error message will automatically disappear once the issue is successfully resolved.

    i dont know why
    ——————————————–
    resolved i change port in database options on 1121 O_o

    but page caching is anyway

    <!– W3 Total Cache: Page cache debug info:
    Engine: memcached
    Key: w3tc_2336b9214d1216baf4a00089ce5fec5d_page_6666cd76f96956469e7be39d750cc7d9
    Caching: enabled
    Status: not cached
    Creation Time: 3.505s
    Header info:
    X-Powered-By: W3 Total Cache/0.9.1
    Last-Modified: Sat, 24 Jul 2010 18:55:38 GMT
    Vary: Accept-Encoding, Cookie
    Content-Encoding: gzip
    Content-Type: text/html; charset=UTF-8

    try see debug from 3 PC but Status:not cached for any page

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    I can’t help you with the information you’re providing. Submit a bug report from the support tab of the plugin if you want.

    Database caching is not working properly. Memcached server(s): localhost:3306 may not running or not responding. This error message will automatically disappear once the issue is successfully resolved.

    This is completely clear, either your server is not running or you have the wrong hostname/IP and port.

    While this error exists, caching won’t work. This functionality has existed since v0.5, there are no bugs here.

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘[Plugin: W3 Total Cache] caching dont work’ is closed to new replies.