AAPT Usage Meter

Notice: (2009) I’ve not been An AAPT customer for awhile now, My usage meters listed here may no longer work, I will not be updating them in the future.

This post has been sparked by the fact that 17 out of the top 20 search queries which direct people to my blog in some way relates to AAPT and its usage meter.

At present AAPT are making a move to a new platform, as such, some new users are on a different system, and the links outlined in this post may not apply to them.

AAPT Official Usage Meter

The official usage meter is available here: https://dialup.connect.com.au/cgi-bin/subscribers/index.cgi.

The username is the main Email address you have with aapt, and the password is the same as for email.

There are 2 main views in the usage meter, Show ADSL Usage & Show Dialup Usage, in actual fact, Dialup usage will show ADSL usage as well. The main difference betweeen these is that ADSL usage only shows a graph with when the usage took place, not many other details (and from what i’ve found, takes ages to load). However the dialup usage page will show much more information, however is all text, i suggest you give both a go and you’ll soon work out which view you prefer.

This usage meter is generally running ~24 hours behind, this is because the usage is counted once your session ends, A Session is the time that the modem is connected to the service, generally a few minutes before midnight a new session is started.
The effect of this is that it apears the usage meter is running slow/behind, but infact, the issue is that since the session starts a few minutes before midnight, all usage in that session is registered for that day. Eg:

Session starts at 10th July 11:55pm
Session ends at 11th July 11:55pm
99.995% of the usage most people make in that period has been made on the 11th, However, as it started on the 10th, the usage will apear for the 10th.

Note: If your username/password does not work on this usage meter, none of the following usage meters will work either at present, this means that you are on AAPT’s new platform.

My AAPT Adsl uage page

Available here: http://dd32.id.au/aapt/

This uses the Offical usage meter for the data source, but i prefer its layout for viewing on the web.

There is a DEMO page here.

Usage Agent

Available here: http://members.optusnet.com.au/usageagent/.

Usage Agent is a .Net 2 application to run on your home computer, its flexible in that you can have it generate an image, work in the tasktray, or merge itself into the wallpaper.


Usage Agent

Firefox Extension: Net Usage

Available here: http://netusage.iau5.com/

I dont personally use it, however some people find this a good option.

Final Note on the new System

A Final note to those people on the new system (Ie. cannot log into the above official usage page)
AAPT has recently changed their website format, and moved to a new platform, all these usage meters are incompatible with the new format.

Instructions to log in with the new system:

If you are using the new system, instructions below:
1. Log in to Help Yourself on aapt.com.au
2. Click See What I’ve Used in the 2nd column
3. Click on your broadband plan
4. Your usage should be shown here. Quantity sum shows your total usage for the month.


dDeviantArt Announcement

EDIT: A number of bugs were present in 0.1 as expected, a Beta of 0.2 is now available, If the plugin doesnt work for you, try this beta version:  http://dd32.id.au/files/ddeviantart-0.2.zip

I’m proud to present to you, dDeviantArt 0.1.

dDeviantArt is a WordPress plugin designed to integrate your Deviations from DeviantArt.com into your WordPress blog.

The main features are:

  •  The ability to have Multiple Widgets predefined, This allows you to quickly switch between the Deviation set your displaying (Or to display multiple Widgets at once)
  • In-line Deviations, You can post deviations inside your Blog post by simply including the :thumb: string which is located on all Deviation pages
  • Portfolio Pages, You can define an unlimited number of “Portfolio Pages”, These pages allow you to show off upto 24 of your Deviations on a single page.

The plugin allows you to either set a RSS feed of the Deviations you want to display, Or allows you to set the Search Criteria when defining a page/widget, This allows anyone to quickly set up the item to display as they please.

More information(And Demos) will be available on the Plugin Homepage, You can download the plugin directly from here.

All comments are welcome, Feature requests, Bug reports, etc, may be submitted via my Contact page.  This is my first Released Plugin, So hopefully you’ll like it.



Download Link  WordPress Plugin competition DeviantArt News

Week 7 status report

Whats been acomplished this week.

  • Integrated the Plugin Search page with the Plugin Installation pages
  • Added a few filters/actions here and there
  • Plugin installation page checks requirements before installing plugins(If requirements are available from wordpress.org)
  • Started the ball rolling for the wordpress.org integration server side.
  • A Few misc. other things.

Plans for Next Week

  • Improve Plugin Installation methods
  • Improve FS options (And the Options page for it)

Problems Encountered so far (And useful resources)

  1. #4639 came into play this week, in short, the “admin_print_scripts-plugin_folder/plugin.php” doesnt fire if the plugin is in a subdirectory.. Was found as the issue while looking into westi’s comment here: gsoc-week-5-status-report#comment-52

This week was a rather slow week development wise, and this blog entry is running late too, Hopefully next week there’ll be more to report on.

Week 6 status report

Whats been acomplished this week.

  • Started putting together a linux box for testing purposes, the VM was becoming rather clunky in performance, Slackware+Apache2+PHP5(module), also plan on doing PHP4 and hopefully safe mode on/off, and perhaps even PhPSuExec if i can manage them all.. I can handle Virtual Hosts OK, just not yet sure on how different PHP settings will work.
  • Removing Serialized data support, moving to XML.
  • Added Ajax loading of next page worth of Theme Search results
  • Started the Plugin Search interface
  • Cleaned up a bit of code.
  • Added a few filters/actions here and there
  • Few minor modifications of the Requirement checking

Plans for Next Week

  • Continue tidying up the plugin search pages
  • Add Plugin installation methods
  • Improve Filesystem handlers
  • start investigating what needs to be done to achieve a plugin/theme upgrader
  • Add more filters and hooks into the code
  • Start writing some documentation on the hooks
  • Start PHPDoc comments for the filesystem handlers(Only in the Direct filesystem class for now, the others are functionally the same) as well as any other functions.
  • Continue testing under other environments, If someone would like to do testing for me, get in touch.

Problems Encountered so far (And useful resources)

  1. PHP XML Functions contain no useful method to convert XML into a flat array simply, theres the option of several PEAR libraries, or simply using preg_match (Which i have done for now).
  2. Bug #3002 affected my only tester this week.. turned out to be the reason the last plugin he tried didnt work as well.
  3. The documentation which explains adding a hook into a plugins code is rather lacking IMO, It took me awhile to find something which could explain a action with multiple arguements, Infact, I think Ihad to do a grep over the WP source code in order to find something, Writing up documentation isnt my strong point, but IMO a good chunk of documenation needs to be written on the codex.
  4. Oh, and TinyMCE suddenly breaking into non-breaking spaces again, Someone got a plugin to strip out non-breaking spaces?, Else i’ll write one next week.

Week 5 status report

Whats been acomplished this week.


  • Started working on “wp-Update-Manager”, a manager for Plugin authors who want to host the Update system themselves.
  • Changed the method that Requirements are checked in wp-Update, also a few small display changes


  • Continued working on wp-Update-Manager, Sorting out weird JS Bugs.(more on this later)


  • Wp-Update-Manager: Can return a Serialised array containing update information for any defined plugin.
  • Wp-update: Handles the update text logic better now
  • Wp-update: retrieving update information from custom defined source works OK (Plugin URI: http://…./)


  • Wp-Update: Fixed a bug with the comparison of Versions
  • Wp-Update-Manager: Slugs not name in url.
  • Wp-Update-Manager: Added a table of Update URI’s.
  • Wp-Update: Major Fix: When running with “short tags = On” you would be greeted with a nice Fatal Error Syntax notice.. oops, all my dev. machines have it turned OFF (And so should you!)


  • Wp-Update-Manager: Fixed a few JS bugs
  • Wp-Update: Added more comments, reviewed the function layout.
  • Wp-Update: Added support for checking if a PHP Extension is available, Implemented a stupid search for version functions from that extension to determine if compatible.
  • Wp-Update: Started some work on the Plugin search UI.
  • Started the ball rolling with getting a data access method into wordpress.org

Plans for Next Week

Hopefully finalise the API, Get some API/hooks into the plugin to allow extra manipulation by other plugins and what not.

Continue with the Documenting of code (PHP Doc commenting), possibly start work on plugin install proceedures(Should use most of the Theme installation code, so shouldnt be that hard).

Investigate bbPress a bit more, I had someone enquire about the possibility of adapting my plugin to work with bbPress, From what i can see it’ll require writing another front end for it, but other than that, it should be possible to re-use all the back end code if i continue into that. Of course at a latter time i’ll be wanting to test with WordPressMU as well.. i’m not sure if theres any major differences that would need to be taken into consideration there.

Problems Encountered so far (And useful resources)

  1. The JQuery tabs plugin cant handle tabs being dynamically added.. Wrote my own version for another plugin i’m working on, Copied it intowp-update
  2. Realised the Tabs JQuery plugin i wrote cant handle multiple tab sections on a page, Added a namespace holder to each tab group.. Started looking ugly at that stage.
  3. Attempted to work out how to create a custom permalink; Custom Queries (Codex) came in useful there..
  4. Ran into a bug with register_activation_hook(), traced it back to plugin_basename() not working on Windows Systems, Turns out its a 11 Month old bug(#3002), Apply the changes from another ticket #4408 and submited a diff back to #3002
  5. More JS Bugs; Remember, Do not create multiple divs with the same ID… JQuery doesnt like it.
  6. Need to work out how to encue jQuery for a single subpage rather than globally into every option page. (check $pagenow, and then check $_GET[‘page’])
  7. Locating the function to create a slug, For future reference, its sanitize_title_with_dashes() no mention of “nicename” or “slug” to be found :)
  8. Completely unrelated to this report, But, Whats the go with TinyMCE breaking out into non-breaking spaces randomly? dont like having to copy-paste to word, do a find replace, and then copy back to code view..

Note: Week 4’s status report was Null and inserted at the end of Week 3’s.

Week 3 status report

Whats been acomplished this week.

Wed:More Filesystem code was written; Specifically find_base_dir() for the FTP class, It should allow the class to find the installation directory on _most_ setups..

Thu: Using the file_base_dir() ftp function i can now install themes via FTP(Using exact same code for both Direct and FTP access), Can also provide a custom base dir in the options panel.

What i’d like to accomplish next week

Complete my Exams :)

As for on the GSoC project, i’ll start to complete what’s been sitting there for the past 2 weeks needing to be done..

EDIT: Week 4: Nothing was done, Exams took priority. Week 5 is now starting, and i’m back up and running.