The automatic backup feature has been slightly modified. Now it only sends you an email if you have edited any part of your logbook during the backup interval. For instance, if you have requested to get an auto email backup sent to you monthly, you will only get an email if you have edited some part of your logbook in the past month.

The FlightLogg.in' Forum has moved. You now no longer need to resister a new account for the forum. The new url is http://flightlogg.in/discussions

UPDATE: Also, if you're wanting a copy if your old FlightLogg.in' data, sending an email to info@flightlogg.in won't work currently as the email system is currently down. Make a forum post instead for the time being.

There has been some recent enhancements to the way FlightLogg.in' handles planes. First off, you can select to make certain planes 'retired'. This means they will no longer show up in the plane dropdown menu on the new flight popup window. This is useful for when a plane gets sold and it no longer comes available to you, or if the plane changes, and therefore a new entry for that tailnumber is required. Instead of having duplicate planes with the same number show up in the dropdown, you can retire the old one so there's only one.

The next addition is the ability to make a plane hidden. This makes all flights in that airplane hidden from FlightLogg.in's site-wide aggregate pages. If you are the owner pilot, and you don't want the flights you log in your own plane to show up, then you can just mark that plane in your 'Planes' section as hidden. All though this will not prevent flights logged in that tailnumber from other people from showing up in those pages.

And the third enhancement is the ability to define a plane's default fuel burn. The fuel burn field on the flight section was originally designed to enter actual, measured fuel burns. The problem was that many users were adding estimated fuel burns in that column when the plane they flew had no way to actually measure the fuel burned for the flight. For instance, people were putting "6 gph" for all flights in a C-172, even though it is unlikely they actually had a measured fuel burn of exactly 6.0 each time.

Now, if the plane does not have a way to measure fuel burn, then it is recommended you enter the estimated fuel burn on the plane section of each tailnumber you fly. This way, all flights you log in that tailnumber will use that default value if no exact fuel burn has been entered on the flight popup. This has the benefit of not making you enter the same value in the new flight popup every time, as well as separating the actual measured fuel burn numbers with estimated fuel burn numbers.

In the fuel burn columns on the logbook page, all estimated fuel burns calculated from the value associated with the plane will be depicted in gray. All measured values that are entered from the flight popup will be depicted in black.

FlightLogg.in' now supports gravatars! You may have noticed a strange monster image in the top left corner. That is your gravatar. If you want to change it, you must go to Gravatar's website, sign up for an account, upload a photo, crop it with their cropping utility, then make sure your flightlogg.in email address matches your gravatar email address. The image is to make it easier to identifiy your logbook from others'.

The colorized states maps were updated today. They are now automatically updated every six hours, instead of you having to manually update them. Also, the corners are transparent, so they look a little better when displayed onto a non-white background. One important thing to note is that the urls for all maps have changed. So if you have one of these images linked somewhere, the image will still work, but it will not be updated anymore.

Over the past few days there has been some improvements to the HTML code which allows for better rendering in older Internet Explorer browsers. So now if, for whatever reason, you're still using IE6 or IE7, you can now log in and use the site. IE6 and IE7 are still not officially supported browsers, so much of the site will still be messed up, but at least you can now sign in and have basic functionality. Browsers that are recommended are Firefox 3.5+, Google Chrome, Opera 9+, and Safari 4.

Now when you open the new flight popup, you'll be greeted with a entry field you've never seen before. Below the remarks box, there is a space to enter a fuel burn value. For details on which units are supported, refer to the help page.

You can now elect to receive email backups of your logbook on a daily bases. At midnight each day, the site will send an email to any user who elects to have the daily backups AND has edited any part of their logbook data (flights, planes, records, locations or events) for that day.

With the recent "relaunch" of the new version of the software that runs FlightLoggin', there seems to be some confusion surrounding some things.

Old Flightlogg.in' - The site that used to be located at flightlogg.in as of a few days ago. This site was written in PHP and was either blue and brown, or red and pink, depending on the colors you selected. If you had an account on this site, you logged in with an email address and a password. That site is still operational, at the domain old.flightlog.in. If you want to continue using FlightLogg.in' as you always have, then feel free to continue doing so at old.flightlogg.in. If you wish to 'upgrade' to the new version of the site, then you need to create a new account here using OpenID. Then import your flights over once your new account is made.

FlightLogg.in' Beta - This site was green, and was found at the domain beta.flightlogg.in from August to about three days ago. If you had an account on that site, you logged in not with a password/email, but by OpenID. All accounts on the beta have a username. By default your username is something like "openiduser118", unless you explicitly changed it in the preferences page (in some cases a custom, non "openiduserXXX" username is created for you if you used one of the 'better' OpenID providers such as AOL or Yahoo). The beta is basically the site you're looking at right now, just it's no longer called "beta" anymore.

New FlightLogg.in' - What you're looking at right now. The only way to log into this site is with an OpenID. If you had an account on the Beta, your account is still there. BUT if you happened to use Google's OpenID service (which is pretty much everybody), your account is inaccessible because of the way Google's OpenID process works. Since the domain name changed from beta.flightlogg.in to just flightlogg.in, Google is returning a different OpenID 'result' which the site can't match with your beta account. Instead it creates a new, empty account. If that is the case, you need to email info at flightlogg.in with your beta username (such as "openiduser23") and your new username ("openiduser187") and I'll swap the OpenID's, then you'll be on your merry way.

Basically if you never participated in the beta, then you need to create a new account and then copy your flights over.

It appears that the way Google's OpenID authentication works, it returns a different value depending on the site's URL. So if you signed up to beta.flightlogg.in with your Google account, then tried to login after the beta replaced the old PHP site, flightlogg.in will create another account, rather than log you into the account you had for the beta. This is only a problem with people who used Google's OpenID (which currently is about 75% of all users).

If you are experiencing this problem, either reply to this thread, or email your old username, and the new username to info-at-flightlogg.in.

Note: This only applies to people who participated in the beta. If you're coming straight from the "blue" PHP site, all you need to do is create a new account, and then import the flights over by following the directions in the Import section.