Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter zombiitv

    (@zombiitv)

    Total hack but this works. Instead of calling the action I’m just calling file_get_content($url). This will load the page from cache if it’s already built or build a new one if it isn’t (just like if you visited the page), if you want it to replace an old page, you’ll need to call prune first. I.E.

    prune_super_cache( $cache_path . 'supercache/' . $postURL . 'index.html', true, true );
    prune_super_cache( $cache_path . 'supercache/' . $postURL . 'index.html.gz', true, true );
    file_get_contents($postURL);

    The problem here is pretty straightforward. WordPress 3.0 includes the 1.7.3 jQuery UI library, everybody here is trying to use the 1.8.7 and they don’t play nice with each other. One of the suggestions above is to replace the core files then hack into the code. It has been my experience that 99% of the time you can do what you need to with WordPress without hacking the code.

    Answer:

    deregister the 1.7.3 files and manually register the 1.8.7 ones should look something like this

    wp_deregister_script(‘jquery-ui-core’);
    wp_register_script(‘jquery-ui-1.8.7′,WP_PLUGIN_URL.’/js/jquery-ui-1.8.7.custom.min.js’);
    wp_enqueue_script(‘jquery-ui-1.8.7’);

    hope this helps people out.

    Thread Starter zombiitv

    (@zombiitv)

    wget worked – thank you

    Thread Starter zombiitv

    (@zombiitv)

    I added this to the cron line “> cronjob.log 2>&1” to try and get some debugging – is this right? Not very familiar with cron jobs yet.

    I’ll look into the wget

    I don’t understand your comment on this being a paid gig for me – what does that mean?

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