Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thank you Ipstensu. I’ll try that variation of curl (my example above had slightly different syntax).

    Cheers.

    This thread has been helpful, but I’m not sure the best solution.

    My site is at Dreamhost, and I used their cpanel ui to set up a cron instead of doing it directly.

    Below are what I’ve tried and the log file results (from access.log).

    1. Using wgetn(roughly per Hack Repair Guy):
    command: wget -q –delete-after https://annieandre.com/wp-cron.php

    log file: 5.119.198.89 – – [19/Apr/2013:23:50:01 -0700] “GET /wp-cron.php HTTP/1.0” 200 194 “-” “Wget/1.12 (linux-gnu)”

    2. Using curl (from Chris O. above):
    command: curl -I https://annieandre.com/wp-cron.php?doing_wp_cron

    log file: 75.119.198.89 – – [19/Apr/2013:14:00:02 -0700] “HEAD /wp-cron.php?doing_wp_cron HTTP/1.1” 301 218 “-” “curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.15 libssh2/1.2.6”

    3. Using php:
    command: /usr/local/php5/bin/php -q /home/username/annieandre.com/wp-cron.php

    log file: Warning: require_once(./wp-load.php): failed to open stream: No such file or directory in /home/username/annieandre.com/wp-cron.php on line 26

    Fatal error: require_once(): Failed opening required ‘./wp-load.php’ (include_path=’.:/usr/local/lib/php:/usr/local/php5/lib/pear’) in /home/username/annieandre.com/wp-cron.php on line 26

    4. Last, here’s the log file output before I disabled wp-cron.php in wp-config:
    75.119.198.89 – – [19/Apr/2013:03:53:15 -0700] “POST /wp-cron.php?doing_wp_cron=1366368795.4622540473937988281250 HTTP/1.0” 200 158 “-” “WordPress/3.5.1; https://www.annieandre.com”

    So the php method in the cron cpanel throws an error. The curl gets a 301 then a 200, a little odd and I’m not sure why. Right now I’ve been running the wget method for about a day and that seems fine.

    Thoughts? Leave it with wget?

    Again thanks to all for posting suggestions above.

    Short version of the solution for that worked for us: deactivated the ShrimpTest Plugin and all was fine.

    Long version: we were having the same problem as described by very first poster.

    Setup:
    1. Using WP 3.1 on XP computer (me) and on Windows7 (wife)
    2. In IE8 the Visual Editor worked fine.
    3. Firefox and Chrome the Visual Editor showed no buttons and text was white.

    PHP was already 5.2 and changed to 5.3 (per user controls at host site). Nothing. Also tried a php change to the .htacces file that someone mentioned, but that hosed a bunch of stuff so I undid that. Reinstalled WP. Nothing worked.

    Finally did the tedious drill of checking the plugins (wife has 30 of them). Per Murphy’s Law, the last plugin I reactivated broke FFx and Chrome, but at least I found the cause.

    Good luck,

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