Jetpack Takes WordPress Stats into its Fold

As you might have noticed if you updated your WordPress plugins today, WordPress Stats has been added to the Jetpack plugin package and all future updates to WordPress Stats will now be done through Jetpack.

Once Jetpack is installed it is safe to deactivate your old WordPress Stats plugin before authorizing Jetpack’s connection with wordpress.com. If you’re using multi site you will need to authorize Jetpack to connect to wordpress.com on a site-by-site basis.

Glorious Errors

Jetpack might hit you with a couple of errors when you try to connect it with wordpress.com. You might get the famous white page of PHP errors showing missing plugin files or you might get the “xml_rpc-32700″ error or the “site_lang_missing” message. The glitches look something like this:

If you’re running a multi site and the PHP error screen displays during authorization then you’ve probably used the network admin panel to disable and delete plugins while they were active in the site that’s throwing you the error. You can fix it by viewing the “Installed Plugins” panel of the site that caused the error. This will force WordPress to disable the plugin for that site.

If you get the PHP error messages while not using multi site then I recommend you reinstall the plugin mentioned in the error messages. If you can’t access your admin panel to reinstall the missing plugin just download the plugin’s file from wordpress.org and upload it to your site’s /wp_content/plugins directory and unpack it before retrying to authorize Jetpack. You should be able to remove the plugin again once Jetpack is authorized.

The xml_rpc-32700 error can be caused by a caching plugin. If you have W3 Total Cache installed or something similar then disable it before retrying to authorize Jetpack. I’ve had a lot of problems with W3 Total Cache in the past so recently changed over to Quick Cache which seems to be working well.

The site_lang_missing error is caused by interference from other plugins installed in your site. The clashing plugin either prevents Jetpack from correctly determining the language of your site or it prevents WordPress from correctly announcing the site’s language to plugins that are being installed. So, how do to solve the site_lang_missing error, in order of ease of implementation and least likely to succeed:

  1. Install Kau Boy’s Backend Localization plugin. Once activated, click “Settings>Backend Language” then follow the instructions for downloading and installing additional language files that are shown in the Backend Language page (Spanish worked for me). Once new language files are installed, change your site’s backend language by clicking the language flag at the bottom of the right-hand menu in the site’s admin panel then retry authorizing Jetpack.
  2. Explicitly specify your site’s language by editing its wp-config file. Change the line that reads “define (‘WPLANG’, ”);” to “define (‘WPLANG’, ‘en’);”, replacing “en” with whatever your site’s language code happens to be e.g “es” for Spanish.
  3. When neither the two aforementioned solutions work you will need to temporarily disable all your plugins then re-enable Jetpack and authorize it to connect with wordpress.com. Although I say “all” of your plugins, you can try disabling them one-by-one and if you feel really communicative and helpful you can leave a comment here to let us know which plugin needed to be disabled before Jetpack would connect with the WordPress cloud.
  4. Another possible solution, though untried, is to create an English to English language translation file for Jetpack. Let me know if you need help with this.

On the Subject of Stats Plugins

If you need something with a lot more oomph, say something that lets you know exactly which pages visitors view and exactly how they got to them then Statpress Visitors is what you need. It tracks visitors from their point of reference to their point of exit. It records

  • Referring sites
  • Search engine keywords that lead a visitor to a page
  • All the pages a visitor views once on your site
  • The link clicked to leave your site, and
  • It monitors visitor history by IP

All stats are neatly presented in easy to navigate pages that can be disabled in the plugin’s options screen. Those pages include:

  • Yesterday
  • Visitor Spy
  • Bot Spy
  • Visitors
  • Views
  • Feeds
  • Referrer
  • Statistics.

I’ve had Statpress Visitors running in JournalXtra for a couple of days and I’m happy with it so far.

Get it here for free (wordpress.org). The developer’s homepage is here.

Multi Site users will need the WordPress Proper Network Activation plugin that’s available here.

I discovered another stats plugin that looks pretty damn promising while finding the link to Statpress. I’ve not tried it. It’s called ecSTATic, has lots of options and is found here at WordPress (developer’s home page here). Let us know if you’ve used it and what you  think to it.

Over to You…

What do you think to WordPress Stats? Was it a good idea to combine it with Jetpack? Have your shout and tell tell the world.

Comments

  1. Bjornar says

    I tried the solution to “site_lang_missing” but it didn’t work, althought I tried Spanish. Any other ideas? Cheers

    • says

      Use an FTP program or your hosts file manager to browse your site’s directory to wp-content/plugins/jetpack/languages/. This directory is where Jetpack stores its translation files. Now follow the instructions for Kau Boy’s Backend Localization plugin but select an alternative language to Spanish or English.

      Another option is to explicitly set a language for WordPress. Browse the directory that contains all of files used by WordPress. Edit wp-config.php to change the bit that reads/**
      * WordPress Localized Language, defaults to English.
      *
      * Change this to localize WordPress. A corresponding MO file for the chosen
      * language must be installed to wp-content/languages. For example, install
      * de.mo to wp-content/languages and set WPLANG to ‘de’ to enable German
      * language support.
      */
      define (‘WPLANG’, ”);Change the bottom line to
      define (‘WPLANG’, ‘en_EN’);ordefine (‘WPLANG’, ‘es_ES’);or to reflect whatever language files you have installed in “wp-content/languages”. The bit that specifies the language used by WP is ‘en_EN’ (for English) or ‘es_ES’ (Spanish).

      If wp-content/languages doesn’t exit (which it will do because you’ve correctly installed Kau Boy’s Backend Localization), create it. Get your language packs from http://svn.automattic.com/wordpress-i18n.

      Now try to install Jetpack again. It’s safe to revert “define (‘WPLANG’, ‘es_ES’);” back to “define (‘WPLANG’, ”);” once Jetpack is installed. Make sure it correctly reflects the backend language chosen for Kau Boy’s plugin.

    • says

      To keep other readers up-to-date, we solved this by disabling all plugins then re-enabling Jetpack before authorizing it to connect with WordPress and re-enabling the remaining disabled plugins. You can view our communication at WordPress by clicking here.

  2. says

    Joseph Boakye  l  am  a  student at Pentecost University Ghana,the  moment l  saw  the mail, l  thought   my  dream has come  true,and so  l printed it  and  went  to us  embassy for  cross   chuck,l  was more  than disappointed when l   fund out  that it  was fake. But l  know  l  will  win one day,josephboakye69@yahoo.com

Leave a Reply