to the wiki
2010-03-12 10:19 pmThe wiki says ljArchive doesn't work with Dreamwidth. That's news to me; within the last week, I imported an old LJ to Dreamwidth and promptly used ljArchive to back it up.
Checked my new backup. Yup, everything's there, and it's not the original LJ version - the comments all say ext_### instead of the LJ URL or username.
I logged into the wiki to change it, but then I realized that I don't know why it was marked "no" for not working. Did someone mark it "no" because ljArchive, known to be picky and stop working at the drop of a hatpin, failed on their first try and they never retried? Or is there some upcoming code push that will break all the API stuff; even though ljArchive works now, maybe it's preemptively labeled non-working because that will soon be true?
Anxious Ree is trepidatious. I decided not to edit the wiki.
For what it's worth: Windows XP, ljArchive 0.9.7, works fine for me. I've had ljArchive toss a wobbly before when it found an incomplete HTML tag in an entry; fixing my markup allowed ljArchive to work again. (I think if you don't have a > for every <, it breaks ljArchive's XML parser.)
If you know, off the top of your head, of an upcoming API breaker, would you reply here, please? I know there are down-the-line plans to retool all the API stuff, but I didn't think there was anything committed just yet.
Checked my new backup. Yup, everything's there, and it's not the original LJ version - the comments all say ext_### instead of the LJ URL or username.
I logged into the wiki to change it, but then I realized that I don't know why it was marked "no" for not working. Did someone mark it "no" because ljArchive, known to be picky and stop working at the drop of a hatpin, failed on their first try and they never retried? Or is there some upcoming code push that will break all the API stuff; even though ljArchive works now, maybe it's preemptively labeled non-working because that will soon be true?
Anxious Ree is trepidatious. I decided not to edit the wiki.
For what it's worth: Windows XP, ljArchive 0.9.7, works fine for me. I've had ljArchive toss a wobbly before when it found an incomplete HTML tag in an entry; fixing my markup allowed ljArchive to work again. (I think if you don't have a > for every <, it breaks ljArchive's XML parser.)
If you know, off the top of your head, of an upcoming API breaker, would you reply here, please? I know there are down-the-line plans to retool all the API stuff, but I didn't think there was anything committed just yet.