This unfortunately broke BPIP's parsers, since (Recently) is not a valid datetime. We'll try to get it corrected as soon as possible.
I'm sorry about that. Profile parsing
did cross my mind, but what made me feel okay about it was that I noticed in the SMF code that non-datetime text was already possible for that field before this patch (the text "Never" can be displayed there, too), so I guessed that you must already have made your parser(s) robust against non-datetimes.
