Today I have an important little bugfix release for djson available.
The issue was, that reading a value after an invalid set, breaks the reading. Thus, if you did a djInt on a value, which does not exist, any later dj call does not work. Thanks to
Raphinity for reporting the issue.
Zamaroht reported a strange issue, when setting a value between two append-operations. This was due to a problem with the caching algorithm and has been resolved! Thanks Zamaroht for the report!
Another problem occurred, when you tried to write a string containing " (quotation marks). Those are escaped now properly, too.
These issue are of course fixed with the latest version djson 1.6.2 download.