Billable 1.2.1

Billable 1.2.1 is out and fixes just one bug. If you were billing a client using time-based services at one rate and later changed the rate default of that client to something else Billable (during the migration to 1.2) mistakingly changed the older services to the current rate. You can notice this since those old invoices would have a new total due even-though you’d expect them to be paid in full.

If you want to re-migrate from the database as it was in 1.1.2 follow these instructions:

  • Make sure Billable is not running.
  • Go to the Application Support folder:

/Users/[you]/Library/Application Support/Billable/

  • Rename the current Billable.sqlite to something like Billable-old.sqlite.
  • Copy the file in the folder Backup named “MigrationBackupSchema7To8.sqlite” to the parent folder and name it “Billable.sqlite”
  • Download the new build and install it:

http://media.clickablebliss.com/downloads/billable/Billable_1.2.2.dmg

  • Run the new build. It will ask to migrate your data, let it and then check the results to see if it fixed the issue.

I’m really sorry to see this bug make it into the public release. I’m very serious when it comes to the user’s data (as this isn’t a simple bookmark file or anything ornamental). In fact the bug isn’t really in the migration code at all, but the result of a feature I added that I have to now re-engineer. Anyways I’m sorry if this bug has effected you. Please let me know if you need anymore help.

Posted on: September 12, 2007 – 4:56 pm

2 Comments

  1. Guillaume Rischard wrote:

    Thank you for your quick reaction and effective fix.

  2. Nathan Bowers wrote:

    For Billable 1.2.3 there is a final additional step.

    You have to re-rename Billable-old.sqlite to Billable.sqlite and then start Billable.

    Before I did this final step all my data was outdated since it was from whenever MigrationBackupSchema7To8.sqlite was generated.

Post a Comment | Comment RSS feed