The Story of a Plugin – Part 4: The FAQ

You may wish to read Part 1, Part 2 and Part 3 first where I talk about the idea for the plugin, early proofs of concept, and getting to the current release version.

There have been quite a few questions about the plugin, so I’ll try to answer some of them here.

What is Pro Blog Stats?

It’s a WordPress plugin that pulls in publicly and privately available statistics about your website(s) / blog(s) and pulls them into your WordPress dashboard.

What version of WordPress is required?

Version 3.1 and above is preferred. It may work on lower versions but that’s up to you!

Any other requirements?

You must have PHP5 or above. PHP 4 will not work, any decent webhost should either easily upgrade you or already be on PHP 5.

How much is it?

There are free and paid versions of the plugin. See our plans/pricing page for more details.

What isn’t it all free?

Gathering the statistics data from tens of sources and storing all that data is quite resource intensive and there is a cost associated with this. It costs us for you to use the plugin, even for the free version, so we have to recoup some of that cost with more intensive plans.

Will this plugin add tracking code for different services into my blog automatically? (Google Analytics, etc)

No, the plugin does not add any tracking code to your site. While it does not require any other plugins to run, you may wish to use plugins for services such as Google Analytics, Clicky, Postrank etc in order to add the tracking code and make the stats available to Pro Blog Stats (if your version supports those stats). Pro Blog Stats will not interfere with any of these plugins as it gets the stats directly from the services themselves and not the plugins.

Why isn’t AWeber included?
This is a common question! We did at one stage have AWeber stats in but their API does not provide a simple count of subscribers by list. To avoid storing any private data we had to do a one-time on-demand calculation that got this statistic. Due to the limits of the API this often failed and brought back incorrect numbers. Rather than provide incorrect numbers we have removed it from the plugin for now.

Do you store any passwords?
No, we avoid asking for any usernames or passwords. Where required we use authentication, like for Google Analytics.

Any other questions please let us know!

One thought on “The Story of a Plugin – Part 4: The FAQ”

  1. This is a great list of resources,Thanks for sharing it with your readers! I can testify to the challenges with finding quality post right now,Thank you for your appreciation! We’d love to hear about any of your successes in this posting.cheap hosting reviews

Leave a Reply