Prepare statement for $result2 also has same issue as $result1 so i’m pretty sure it needs to be updated.
// Update all-time table
$result1 = $wpdb->query( $wpdb->prepare(
"INSERT INTO {$table}data
(postid, day, last_viewed, pageviews) VALUES (%d, %s, %s, %d)
ON DUPLICATE KEY UPDATE pageviews = pageviews + %d, last_viewed = '%s';",
$id,$now,$now,$views,$views,$now ));
// Update range (summary) table
$result2 = $wpdb->query( $wpdb->prepare(
"INSERT INTO {$table}summary
(postid, pageviews, view_date, last_viewed) VALUES (%d, %d, %s, %s)
ON DUPLICATE KEY UPDATE pageviews = pageviews + %d, last_viewed = '%s';",
$id,$views,$curdate,$now,$views,$now ));
Thanks to @hykw and @burateen !
-
This reply was modified 8 years, 8 months ago by antonmaju.
-
This reply was modified 8 years, 8 months ago by antonmaju.
Hi rlamb2,
Thanks for informing this.
Had the same issue, probably it was caused by case insensitivity in my Windows development machine.
Hi @nigro.simone
Here is our page cache settings
We use static front page with custom template so I guess it is the reason the field naming is different.
In this case, I enabled “Don’t cache front page”, which in theory should serve homepage without cache.
@edebe2 , have you found any solution for your case ? apart from purging page cache manually.
@nigro.simone we already have “Don’t cache front page” settings enabled.
