Search results

If you noticed MM go AWOL, it was because I let the domain expire. See over on FT for some more information. It's also available again here (but please see discussion on FT): Mileage Monkey

The MM approach for BA was pretty simple .. there was a 2000 mile threshold to decide between long & short haul TP earning. However BA started to manipulate that .. with exceptions creeping in .. MM didn't cater for these. I was busy with other things for a while and took my eye off the ball...

A couple of points which will hopefully clarify and guide: 1. The SC calculations in MM are typically distance based (I.e. Between X and Y miles distance will earn Z SCs) 2. I am not familiar personally with QF SC earn rates or any changes to these. Feel free to point me at a concise...

Well, i seem to have managed a flight database update. US, UL, JJ and QR are all in and all flights are current. Note that no rule or other changes have been done, but feel free to highlight anything amiss

Never say never :) I may get some time in the next couple of weeks. I'm always open to offers of help - that could be JS programming, or even working out the detailed changes required to update the award/earning scales :). (MM code is hosted on github, but the data (e.g. flights) is not)...

0.95061 is out ... hopefully working for everyone. This version is tolerant of whether addThis is blocked somehow for you - MM will work either way. Please let me know if any issues or if this hasn't fixed it for your situation.

footy99 - can I work with you directly? I'll give you a special link to test and if you can report some info back that may help me figure out what's going on. Won't have this until sometime on the weekend.

Thanks for the info! OK, to confirm, when you try this link, no map & details show? I've just tried this link on a Win7x64 box, using IE9, FF23.0.1, and Chrome 29. All work fine. I can fix a bug when I can repro it - the challenge for me is that at the moment I cannot repro it. Difficult...

I believe I fixed this earlier this week - please make sure you are using v0.95060 and not 0.95059 ... use shift-reload etc. Please report if the issues are still occurring - I have tested various combinations of IE, FF, Chrome, Safari & Win7, WinXP, OSX, IOS and not seen issues now with...

Per other thread, hopefully fixed now with 0.95048. please advise if it's still occurring (in the main thread referenced in my previous post here). Thanks!

OK, apologies...I added a little more error checking at one place in the code, and it seems good now (v0.95048), e.g. this. Please let me know if anyone is still seeing the issue.

Can you please share a URL with me if possible? I.e. copy the "Link to .." link in the sharing section. For example, when I use this: MileageMonkey it reports it as a valid itinerary, and shows the details below as I'd expect. I've tested on FF 13.0.1 and IE8, is it a particular browser...

Does anyone have experience if this applies to multiple guests, or is it restricted to the Plat member + 1 guest? Any further thoughts on whether the H bucket is reliable to check for availability for these upgrades?

0.95042 - Greek Isles, and links to OWE Planner queries Mileage Monkey change log Lots of new Greek destinations

v0.95040 (2012/03/25): Flight updates - added Air Berlin. Lots of new destinations; e.g. HRG, LXR in Egypt (mostly Y only), new ways to AMM & TLV, a direct Europe-HKT service and VRA (Cuba). For getting to these, use the "OWE Planner" section with a "From" of "de" (Germany) - it can be a...

I don't announce all releases here - follow MM on Twitter if you want to see them all.v0.95037 (2011/12/29): Flight updates - new: BGY,CFE,CMF,FLN,GRJ,PCL,PDV,ZPC old: BRC,FLA Removed LGW-SSH (ended April 2011) and LHR-ICN (used during Japan crisis Q2 2011) v0.95036 (2011/11/19): Flight...

As of 0.95033 MM now accepts ',' ';' and '//' as separators to indicate surface sectors (or separate routes!) http://www.slfft.org/mm/award.htm

WebSense is now happy with MM. There was no risk to MM users at any time; WebSense was picking up on something in a comment section. The WebSense test for MM can be found here, it was the Security Categorization section which was giving the warning (the biohazard/magnifying glass icon).

Thanks - I was on the phone to them when you posted that! I have a case open (even though I'm not a customer) and they've advised they should get back to me within 24 hours. I may need your help if this plan doesn't help, thanks for offering.

Thanks - I'm in contact with Websense to figure out how to get it fixed.