Age | Commit message (Collapse) | Author | Files | Lines |
|
version used to process an account data
The problem being that only part of the header section would be re-encrypted, thus ending up with different sections encrypted using different crypto function versions.
And this would break when loading data back on next login.
|
|
- updated reference dates;
- removed reference to Community Edition;
- normalized logging using Clipperz.log[Warn|Error|Debug]
|
|
|
|
Saving preferences was still invoking an old method removed since the unification of the backend
|
|
|
|
Conflicts:
frontend/beta/css/yui-extensions/basic-dialog.css
|
|
Changes that check for a weird condition that was causing cards to get corrupted.
A similar change has been applied also to /gamma (in a different commit, though)
|
|
The javascript was checking for the parameters assuming the backend
provided version information. The community edition backend does not
supply any versioning information so the javascript checks both
locations
|
|
Fixed PHP backend and /beta code to handle request and data format compatible with /gamma.
At the moment adding/deleting/editing records seem to work fine.
|
|
|
|
|