API key

I’m not quite sure why it would have worked on your dev server without the API key since the Jetpack API needs that key to access the information. Very interesting.

The current setup does require that the API key be entered in the widget per site. The way in which you describe how you want to use it tells me I should remove the API key from the widget and put a plugin settings page where you enter the key. This is probably how it should be anyway, plus it would let me implement the other settings I’m working on better. Thanks for the support request so I could think about it this way.

That would be really fantastic. Do you have a timeframe in mind for that?

Until then, I can make a widget, put the key in, and then move the widget to the inactive area?

I see there’s an option in the options table for jetpack_post_views_wp_api_key Can I simply put it in there?

Moving the widget to the inactive area will work just fine after the API Key has been entered. If you feel confident with the PHP code you could just hard code the API key to the options table, though the function to grab all the post view information is only ran either every hour or when you click the save button on the widget.

I would love to get the new version released this weekend, but it depends if I’m able to put in as much time as I would like to.

I’m happy to test or help if needs be. I really need it. ?? Your chosen mechanism for making the data available is wonderful. ??

I’m trying to think of a way to make this work without having to put our API key in. Doesn’t Jetpack already store the API key in the options table? Is there any way to reference that?

I tried that at first, but as far as I can tell, WordPress does not store it’s own API Key in the database at all. I searched for it using PhPMyAdmin, and nothing came up. So I was forced to find it a different way and the api.wordpress.com site is the only way I found. ?? I wish it stored it in the database so I could reference it.

It looks like stats_get_csv() will get the data you need. Something like this:

if (function_exists(‘stats_get_csv’)) {
global $post_stats;
$post_stats = stats_get_csv(‘postviews’, ‘&days=-1&limit=-1&summarize’);
}

It simply asks jetpack for it, rather than hitting the server again.

I tried that function in my dev environment, and it didn’t exist. I never did try it in my production environment though, so I’ll give it a try. But I think that function not existing might be the reason https://www.ads-software.com/extend/plugins/wordpresscom-popular-posts/ stop being actively developed. I’ll let you know what I find later today.

That would make sense, I found yours because posts-n-pages quit working for us.

That said, the function exists in jetpack. I haven’t done any research to see if it’s still working. I can do a post in their support area to see if it’ll still work.

So it seems that the function exists on my production environment, so I can use it as the primary source for the information (it’s more up to date anyway for the stats). I’ll still have options for entering API information if for some reason the function doesn’t exist.

Yep. That function comes from Jetpack, so as long as you have that on your dev machine it should be there.

Are you still thinking of doing it this weekend? I like your method of making the data available more than the plugin I’ve been using.

Ya, the plan is still to get the new version out this weekend.

Awesome, I’ll be on all weekend, happy to test. Can you see my email address?