avatarworf

Thanks, Figured it out… the root .htaccess needed to have my WWW / non-WWW directive first before the list of W3 Total Cache

Sorry the attempt to load a page was to https://www.domain.com/ – it must be w3tc which redirects to the cache page

Thanks Very much..

Here you are; basically it reads IDs from a table; searches an XML document, and updates the records in the table. I’ve removed most of the error checking to make it more readable for you.

<?php
include_once(‘wordpress/wp-config.php’);
#include_once(‘wordpress/wp-load.php’);
#include_once(‘wordpress/wp-includes/wp-db.php’);

$results = $wpdb->get_results(“select id,slug from travel_wp_affproducts WHERE id > 50”);

$ProductList = array ();
$Slugs = array ();

foreach ($results as $id) {
array_push($ProductList, $id->id);
$Slugs[ $id->id ] = $id->slug;
}

$xml = simplexml_load_file(‘wordpress/i/data.wiggle’);

foreach ($ProductList as $prodID) {
$result = $xml->xpath(“//prod[@id=’$prodID’]”);

if ( ! empty($result) ) {

$name = $xml->xpath(“//prod[@id=’$prodID’]/text/name”);
$url = $xml->xpath(“//prod[@id=’$prodID’]/uri/awTrack”);
$price = $xml->xpath(“//prod[@id=’$prodID’]/price/buynow”);

$db_insert = “INSERT INTO travel_wp_affproducts SET id=’$prodID’,\n”;
$db_insert .= ‘name=”‘. $name[0] .'”, ‘;
$db_insert .= “url=’$url[0]’, “;
$db_insert .= “stamp=now(), “;
$db_insert .= “value=’£”.preg_replace(‘/\.00$/’,”,$price[0]).”‘ \n”;
$db_insert .= “ON DUPLICATE KEY UPDATE \n”;
$db_insert .= ‘name=”‘. $name[0] .'”, ‘;
$db_insert .= “url=’$url[0]’, “;
$db_insert .= “stamp=now(), “;
$db_insert .= “value=’£”.preg_replace(‘/\.00$/’,”,$price[0]).”‘; \n”;

$success = $wpdb->query($db_insert);
}

Funny the Development Version I downloaded (just now) didn’t have those modifications (but the patch file looks correct to me.)

Below Plugin Version 2.3 it should create the table alteration – definded as a VARCHAR(64) just in case anybody’s watching their space allocation.

Maybe the Plugin Developer was hoping to do something new in this version but the syntax doesn’t support it. So I guess we go ahead and create the column

Wonderful! under Development version 0.9.7+

Just a note for anybody who had a broken “auto detect” podpress action which causes other problems, add the files definition into the exclude file list in super-cache

podpress_backend\.php

Same issue; I gather the request the tag cloud makes only selects from posts
I think a quick workaround for me will be to create a dummy, back-dated post with all the tags that I’ve used on the pages.

Dito on this. I guess another plugin should be used for this, can anybody suggest one of them?