https://bugs.kde.org/show_bug.cgi?id=515398
--- Comment #1 from Jack <[email protected]> --- Minor point: please do not use "latest" as a version, it is important to specify the actual version. This is important for folks referring back to this bug in the future, when the latest versions will be very different from those at the time the bug was filed. Thanks. You are correct - frozen is frozen, and there is no way within the program to reverse this. You have two options at this point. One is to revert to your most recent backup (you do make backups, no?) The other is to manually edit the data file. (make an extra backup) In the program, you can use "Show transaction details" to find the transaction ID ("T" followed by a long number) and then search for that in the file. i believe (it's been a long time seince I've actually looked) the "Frozen" state is stored either as the value of an attribute or as a key/value pair, but it should be obvious. You can look at the previous or next transaction in the file to see the format for an unmarked, cleared, or reconciled transaction to match. I think (but need to confirm) that there is already a wishlist bug to allow reversing/altering a "frozen" transaction to another state. -- You are receiving this mail because: You are watching all bug changes.
