by admin, 2012/06/24

StatPress Community Pre-Release (formerly StatComm)


StatPress Community (formerly StatComm) provides Realtime Statistics on your blog, collecting information about visitors, spiders, search keywords, feeds, browsers, OS and more. Once the plugin has been activated, it will immediately starts collecting information.  

StatComm provides many views to analyze the incoming users on your blog, and also spy tools to find out their procedence. For users of other StatPress plugins variations, it provides with a well known set of features and information.  Download directly from WordPress Repository

Downloads in WordPress Repository so far: 


  • 1.7.68: Plugin prevent from activation if some conditions are not met. Reapply a fix for a multisite issue.
  • 1.7.67: Fix from several errors. Banip.dat behavior  corrected.
  • 1.7.66: Fix multisite
  • 1.7.65: Few fixes
  • 1.7.62: Minor code improvement
  • 1.7.60: Metaboxes / Shortcodes subplugin
  • 1.7.50: Fixes and preparing Ajax framework
  • 1.7.40: Stabilization release. Bugs fixed  & improve speed.
  • 1.7.30: Subplugin, template system, improved export data. Statcomm will need WordPress 3.3 to run this version.
  • 1.7.20: Multisite edition, tabbed options,  optional delete table on uninstall
  • 1.7.10: Lazy cache, improved performance, extended information on errors
  • 1.7.01: Migration Tool, custom filtering, language detection
  • 1.6.90: Instant Spy + Google Maps, custom action , 404 error control
  • 1.6.81: User Agent String disabled by default. Fixed
  • 1.6.80: User Agent String Database now user controlled and easier to manage.
  • 1.6.70: Instant Spy Information: Ajax tool to provide extra info for the incoming traffic.
  • 1.6.60: First version using Geolocation
  • 1.6.50: Improved User Agent String API, better documentation, uninstall, log library, status panel, fixes.
  • 1.6.40: new class to handle Settings API. Improved code , warnings solved.
  • 1.6.31: patching of few fixes.
  • 1.6.3: new API for getting accurate user agent info. Improved overview, code enhancement. Icons added.
  • 1.6.2: improved code. Compatible with 3.0 and up, widget improvements, now improved and compatible with classes.
  • 1.6.0: launch

TEXT TO CUSTOM FIELD PLUGIN (Released: 2012-03-20)Text to Custom Field Plugin allows you adding custom fields from any desktop blog editor even if the editor can’t support custom fields at all!. This problem was a serious one sometime ago with Scribefire (not anymore) but there are some other blog editors who lacks this feature.

Although this plugin was built with Scribefire in mind, I’m not related with Scribefire in anyway. This plugin will work inside the WordPress editor (although it will be a bit strange to use it in such case, it will work).  

== How to Use it ==

Type anywhere in a post using the following format:   {cf yourcustomfieldname=yourcustomfieldvalue} .  After create or update the post, the custom field will be created.

Examples: {cf thumbnail=} {cf posticon=/wp-content/uploads/posticon.ico} Notes:

  • You can use any number of custom field for post.
  • Reserved characters: ‘{cf‘ and ‘}’,because it conflicts with the delimiters.
  • After the post, the tags are automatically erased.
  • If the custom field is already present, its value will be replaced.

Downloads in WordPress Repository so far: 880

Send your comments through the Contact Page

Support: The WordPress Forum has a Support for this plugin (you need to register to post in the forum).


Another Twitter Updater is a WordPress plugin that allows to send twitter updates to your Twitter account when you add or edit a post. You can optionally decide if you wish to send message when update or create a post. It includes also some filters to process the title text if you wish. Best of all, Another Twitter Updater will work with any weblog client xmlrpc enabled.

==How to use it==

  1. Install in the /wp-content/plugins/ directory.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Go to Tools-> Another T.U. to config the plugin.

FILTER TITLE The plugin allows to filter the message using the twitterupdatermessage filter This is an example you can put on function.php from your theme: function twitterupdateaddtime($content) { return date(‘o-n-j g:i:s’) . “->” . $content; } addfilter(‘twitterupdatermessage’,’twitterupdateadd_time’);

This example will add the date and time on the title. Note that it will add also the text if you put some text on the plugin configuration page. You can see more examples in the anothertwitterupdater.php file (those filters are deactivated) Send your comments through the Contact Page .

There is no support for this plugin, since I would need a complete revamp.

CLONE FREEMIUM : A Thematic Framework child Theme

Clone Freemium is a clone of Freemium Theme converted to child theme to the Thematic Framework It has the same features with extended flexibility and extensibility provided for this framework.

Send your comments through the Contact Page . There is no support for this theme

1 Comment

    • Reply Cancel Reply
    • February 28, 2016

    Good post, interesting ptnois. I have to say that I disagree, however, that noscript equates to a large discrepancy in traffic. Perhaps for some sites that attract a higher density demographic that blocks JavaScript, but for the general web, no, blocking JavaScript isn't a huge impact. The reason here is that without JS most sites are quite unusable. Once a user chooses to enable script for a site, bam, they're tracked.A couple additional thoughts:1) Setup Google Analytics tagless tracking. Yes, this is supported. I do it on my site. You can render the GA mobile tracking script inside a [noscript] tag following your GA tag. You'll now get traffic from things that run script and things that don't. They use completely different visitor and session identification methods, so don't expect the numbers to line up, and do expect a skew to your total data. Perhaps use a different GA web property ID for this tag.2) Bots are BAD. The main reason I think GA seems to be lower is that it is *very accurate* at counting *people* and not counting everything else. In my experience over a decade bots are really clever at looking like normal users so that they can scrape content and do other kinds of nefarious or not so nefarious things with your site. The point is, most tools that don't rely on dual JS+cookies will always show higher traffic, and if you really dig into the data that's logged the delta comes from bots, not people. I've seen this stand out most prominently with Urchin when looking at server logfiles that contain an image hit from a noscript tag and image hits from a JavaScript tag. The result: the noscript tag contains lots of hits from user agents that look like normal browsers, but never show up in the JS, and also miss things that normal real people's browsers have, like plugins in the user-agent string, usage patterns that would come from a person, etc So, to wrap it up, this is a great topic, but honestly I'm pretty tired of hearing complaints about GA accuracy without backing from deep analysis of the underlying factors that go into reporting web stats for all of us who love the stats so much.Best,-Caleb

Leave a Reply

Your email address will not be published Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>