Forum Replies Created

Viewing 15 replies - 61 through 75 (of 94 total)
  • Thread Starter Prx

    (@parneix)

    Thanks for your generous and kind help.

    If anyone has another view on the subject, I’ll be glad to hear it as well.

    P.

    Thread Starter Prx

    (@parneix)

    Hum… I afraid I wasn’t quite clear on that point: I didn’t edit the wp-cron.php file. Never touched it.

    I asked help from my host provider to setup real cron from my cPanel, and then added a line to my wp-config.php file to disable WordPress cron, like so:

    define(‘DISABLE_WP_CRON’, true);

    Thread Starter Prx

    (@parneix)

    Hi,

    Thank you. Yes, I’m perfectly aware of the security issue. Version 0.9.2.5 was fixing a vulnerability discovered in W3TC at the very end of December 2012.

    P.

    Thread Starter Prx

    (@parneix)

    Well, I don’t know if I have actually fixed the problem, but this procedure made the error message disappear:

    In the Minify tab (not in General setting) I have unchecked “Rewrite URL structure”

    That’s it.

    P.

    Forum: Plugins
    In reply to: W3 Total Cache
    Thread Starter Prx

    (@parneix)

    Hi. I would recommend you to start your own thread. You will have more chance to get an answer than by adding a reply to an old thread that is already mark as “resolved”.

    P.

    Thread Starter Prx

    (@parneix)

    Solved! Apparently even though the CNAME checked with mxtoolbox it needed some time to propagate. Twelve hours latter, it passes W3 Total Cache test. My “origin pull” configuration is now working properly.

    P.

    Thread Starter Prx

    (@parneix)

    Follow up:

    The problem does NOT concern all files hosted by the CDN. I made some changes to the footer.php file and after I “purge all cache” it took effect: the changes were correctly served by the CDN. However, changes made to the style.css file still refuse to change.

    Thread Starter Prx

    (@parneix)

    Follow up:

    From the “General Settings” page, when I try to “Purge cache” in the CDN field, it systematically fails.

    P.

    Thread Starter Prx

    (@parneix)

    Hi,

    It’s done, I sent a bug report.

    Please note: I also tried to invalidate the style.css file from my AmazonCloud Front console without effect.

    P.

    Thread Starter Prx

    (@parneix)

    A quick follow up, as this is a serious issue (I can’t modify my theme under my current settings, unless I completely disable by CDN):

    1) I tried to purge my style.css file without effect.

    2) It was suggested to me to created version of the file and allow query strings from by CDN. I guess it’s a solution, but I would love to use a way native to W3 Total Cache to solve this issue.

    P.

    Thread Starter Prx

    (@parneix)

    Hum. I tried it but then the whole website won’t load through the CDN. I will load only if I ask to be served directly (without the cache), as an administrator for example (I’ve asked for the administrator not to be served a cache version: more practical for maintenance).

    P.

    Thread Starter Prx

    (@parneix)

    [SOLVED]

    Well, it’s most likely all solved, I just didn’t test the “Origin Pull” configuration.

    But my “Origin Push” setup is working just fine again. What was the problem? After a bit of research, a lot a results pointed toward the same direction: a bad time setting on the servers where my blog is running. Using SSH commands, I checked the servers time and it was of by about 15 minutes. At first, I didn’t thought much of it: it looked like a small discrepancy. I nonetheless send an email to my host provider asking him to check the time of my (shared) server.

    I got an answer back confirming the 15 minutes delay. I was also told it was fixed. And sure enough, when I tested my CDN “Origin Push” configuration, it works (meaning that in the “CDN” tab, it passed the test).

    That’s it. I’m pretty sure the problem experienced with me trying to setup an “Origin Pull” was linked to the same problem.

    P.

    Thread Starter Prx

    (@parneix)

    Also if it can help:

    1) A couple of days ago I had to re-install my WordPress installation. Everything seems to be working normally except my CDN.

    2) I tried to switch to “Origin Pull” because by settings for “Origin Push” (which were previously working) were not working anymore. Somehow, I think the two problems are related. Here’s the error message I get when I try to test my CDN in “Origin Push” mode:
    Error: Unable to list buckets (S3::listBuckets(): [RequestTimeTooSkewed] The difference between the request time and the current time is too large.).

    P.

    Thread Starter Prx

    (@parneix)

    Also here are the result of my compatibility check:

    Server Modules & Resources:
    
    Plugin Version: 0.9.2.4
    PHP Version: 5.2.17 (PHP5 required for Minify, Rackspace CloudFiles, Microsoft Azure support)
    Web Server: Apache
    FTP functions: Installed (required for Self-hosted (FTP) CDN support)
    Multibyte String support: Installed (required for Rackspace Cloud Files support)
    cURL extension: Installed (required for Amazon S3, Amazon CloudFront, Rackspace CloudFiles support)
    zlib extension: Installed (required for compression support)
    Opcode cache: Not installed
    Memcache extension: Not installed
    HTML Tidy extension: Not installed (required for HTML Tidy minifier suppport)
    Mime type detection: Not installed (required for CDN support)
    Hash function: Installed (hash) (required for NetDNA purge support)
    Safe mode: Off
    Open basedir: Off
    zlib output compression: Off
    set_time_limit: Available
    mod_deflate: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
    mod_env: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
    mod_expires: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
    mod_headers: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
    mod_mime: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
    mod_rewrite: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
    mod_setenvif: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
    WordPress Resources
    
    /home/user/myblog.com/.htaccess: OK
    /home/user/myblog.com/wp-content: OK
    /home/user/myblog.com/wp-content/uploads/2012/04: OK
    Fancy permalinks: /%postname%/
    WP_CACHE define: Defined (true)
    URL rewrite: Enabled
    Network mode: No
    Thread Starter Prx

    (@parneix)

    Also, since I’ve installed and activated the plugin, I now get some intrusion alert to my /wp-login.php page from an IP address in Turkey which is already listed as being suspicious (and no, I don’t live in Turkey).

    What should I do? Can I ban this IP address and should I do it?

    Thanks,

    P.

Viewing 15 replies - 61 through 75 (of 94 total)