This is a revision of a previous question I submitted, with more information.
IMPORTANT EDIT: I found that the problem is not what I thought it was, and the error should now be easy to reproduce. The problem occurs when the built-in
edit journal privacy tool is used. I have edited this entry to reflect this fact, and removed misleading references
(
Read more... )
Comments 7
Do you have any sort of odd backdated entries? It sounds like the type of behavior you get on databases sometimes when a database index is screwed up, I'm trying to think of any possible cause...
Reply
Since syncitems also returns comments, could unusual behavior result from an edited comment? Has anyone tested how syncitems treats edited comments? (Comment editing has been around a while, so I'd expect so...)
I don't know how the LJ database is built... Chances are that if there's a strange thing you can do to a journal entry, I've done it. Without knowing how the database is built, however, it's hard to know what would be likely to cause a problem. If you think it would be useful, I could create a dummy journal and do some testing.
Reply
I made a test journal oak_and_sage. I tried various things, and as soon as I used the built in LJ "Edit Journal Privacy" tool to set all its public entries to friends only, the syncitems call started hanging.
oak_and_sage only has 7 entries, all of them test entries. Two were converted from public to friends only.
I did this on my real journal (this one) prior to finding LJ-SEC. Apparently, this causes problems.
Reply
Reply
Reply
Reply
Leave a comment