Announcing Stat Traq Beta ‘a’

A little over a week ago I wrote about ‘Powdered by WordPress’ which Matt linked to. In that post I mentioned a statistics package I was working on and how I was going to release it to the public as a plugin. Several folks mentioned that they were interested in trying it out. That package I have officially named ‘StatTraq’ [someone please let me know if that name is taken, I could not find any evidence that it was]. StatTraq is in need of testers who can install the WordPress 1.2 plugin (following the included instructions and installer PHP page) and then report the bugs they find. Also, those who use it are asked to submit feature requests and ideas for future expansion of design and functionality. Suggestions and problems should be sent to stattraq@randypeterman.com.

Download the Zip file: wp-stattraq.zip

3 thoughts on “Announcing Stat Traq Beta ‘a’

  1. Ah! The installation instructions are buried deep within the installation itself–but it’s not an impossible task.

    In fact, it’s rather easy. Despite the cautions you gave re: checking all paths & table-names are valid–all of mine were, and it worked straight out of the box.

    a VERY pleasant experience!

  2. Wow, still pretty rough. It sure looks to have some good promise. I should note that the query string tracker throws a MySQL error. Easy fix though, in query_strings.php on line 89, the FROM table is wrong. You have it in there as logger, for me replacing that with b2stattraq did the hitch. Obviously you will want a way for this to link back to what is actually created for each person.

    The install directions I found a bit off, I imagine you wrote them before you finished with your release product. Since there is no: stattraq-config.php file.

    Shows excellent promise!

  3. Thanks, yes this has been fixed for the next beta, which should be out by the end of this weekend (Monday the 12th at least). I like to give the betas a little time to get debugged so I can fix more than one bug between releases.

    I have fixed this bug and several other bugs for the release and am adding a link back to the blog root as well.

Comments are closed.