jruca

Thanks for quick response. Your explanation makes complete sense and certainly clarifies why and when the unique key was dropped. Thank you for the information.

As we are only concerned with the last two weeks rather than hourly or smaller, I was able to merge the existing summary records and add a custom key to the table to allow updates rather than inserts. This will work much better for us and greatly reduces database load (56K vs 4M records and 0.05s vs 7+s for the LEFT JOIN with wp_posts).

With that being said, do you plan to keep the ON DUPLICATE KEY UPDATE part of the view count update in future releases?

Thanks again for the response and the great plugin!

We have updated to 1.9.6 and all works great. Thanks again for taking a look at this issue.

This particular issue is fixed in the latest release. However, I am not running multi-site so the “slug is duplicate in return url” bug fix makes the update unusable as it uses get_blog_details(), which is not loaded in the single site environment. I wrapped that update in if( is_multisite() ) and all seems well.

Thanks again for this great plugin and support for these fixes.

Great! And thank you for this awesome plugin. It has helped with our project tremendously.