This is part of the views tracking table that can be enabled with this constant in your wp-config.php:
define( 'PODS_AJAX_VIEWS_STATS', true );
The plugin is somewhat barebones in terms of the admin area, sorry for the rather unhelpful error there, instead of a proper message. I’ll be sure to add messaging to that effect soon.
Once you enable that constant, you’ll want to deactivate / reactivate the Pods AJAX Views plugin to get the table setup.
Thank you for your response, but I followed the directions and still get the same error.
Try deleting the pods_ajax_views_version option in your wp_options table, sorry about that, it only runs that activation/upgrade routine on updates. I’ll shoot out a new update for the plugin this month.
Hmm, I tried that, uninstalled, reinstalled, activated, still no wpsr_podsviews table. It’s odd, but when I go to the plugin editor and select the pods-ajax-views.php file it says “(active)” but when I select the file Pods_AJAX_Views.php it says “(inactive)”.
I tried changing the name of the latter file and reference in the former file, in case there was some OS inconsistency, like case insensitivity in file names, but it doesn’t seem to have helped.
Your code looks fine otherwise, as far as I can tell.
If you know SQL, you can create the table directly with this query:
https://gist.github.com/sc0ttkclark/f930824637b51c01b090
Ahaa, ok when I did that I got an error: “Specified key was too long; max key length is 1000 bytes”
Hmmm, now I get this error: “#1072 – Key column ‘cache_key(255)’ doesn’t exist in table”
I tried taking out the “(255)” on both cache_key and uri, but we are back to error, “#1071 – Specified key was too long; max key length is 1000 bytes”
Do we need that compound Unique Key?
I removed that part. At least the table is there now.
Yeah, weird that it was causing that issue, I’ll have to fix that in the plugin itself.
I can see the page now, but there doesn’t seem to be any AJAX views nor a way to create any. Is that normal, or is it because part of the plugin is not running?
You don’t create them, you use pods_ajax_view( 'my-big-cached-template.php' ); to call them, just as you might when you call get_template_part(), it looks at your theme (or child theme) for the file at that path.
More information can be seen here: https://ww.wp.xz.cn/plugins/pods-ajax-views/
Pods AJAX Views makes use of pods_view(), it just AJAX loads them in after the page loads initially.
