Wow!!! This is wonderful!! I never thought I'd be able to archive comments! And search them? This is amazing. I only have 8,682 comments so I'm not your iron user but it handled all 8,682 without breaking a sweat. Thanks so much!

I'm glad you like it! I have a few revisions to go before I'm satisfied with it - mostly bug fixes and robustness issues.

I don't know if you are still interested by the LJBook PDF output.

I have updated the backend for XML files. (Comments should be well rendered (it wasn't the case before)).

http://www.ljbook.com/xml.html

Let me know if it's OK or not...

Hi gads,

Of course I am interested! I heard your service is getting moved onto LiveJournal proper (congrats!), but I imagine that will lessen the need for ljArchive.

I tried the comments export and LJBook gave me blank PDF's. The error could be on my side - I'm not sure. I am going out of town but I'll check it out when I get back.

Keep up the good work with LJBook.

I think that ljArchive is still interesting (and will be)!
Once LJBook will be moved to LJ, you could just put a "create a PDF" button that would send directly the XML to LJ servers
OR
IDs of unmodified posts and an XML with some entries modified to print.

I have unchecked some basic checks (like root_node==blogbooker).
Let me know...

I have yet to get the latest version to work on my home computer. Works fine at the office but not at home and, usually, my internet connection is better at home than at work! Both machines WindowsXP, IE6 and the other version worked fine on the home machine.

Here's the error that your handy dandy error copier copied - any clues as to what I should tweak, reinstall, eat for dinner?

ljArchive Error: Error trying to generate a session: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, String methodName, Object[] parameters)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(String MethodName, Object[] Parameters)
at XmlRpcProxy4844767e-e55c-40c8-a2b8-3675fcced015.SessionGenerate(SessionGenerateParams )
at EF.ljArchive.Business.Sync.GoThread()

This is making me nuts! I've uninstalled and reinstalled. I've reinstalled the .Net framework and I still get the same error message (only now I get it faster!)... I hate to wipe out my db of entries and I cannot imagine that's causing a problem. Suggestions? I really want to have this at home...

Hi susan,

I'll have to take a look at it this weekend - the exception info you've provided should be all I need.

The client doesn't yet provide very informative error messages - ones like what you've received will eventually be paired down to things I can control (like a bug in the software) and things I can't control (like livejournal being down), with appropriate messages for each.

In the mean-time, thanks for being patient. You'll hear from me soon!

Now that I know you are on it, I got patience to burn. Plus I've got my copy at work for emergencies :)

I did suspect the culpret was LJ so I waited until I could get a good response from LJ for a sustained time and tried LJArchive then but I got the same error.

Turns out I am genetically unable to leave anything alone :)

I sync'd up my work version and then brought the xja file home. I replaced the xja that I had on my home computer with the one from work and it loaded fine. So, I clicked on 'sync' and guess what??!!! It Sync'd!!! Brought in the new items since the work archive was created!!!

It's fixed! So, it just wasn't happy with the old xja! Wild, eh? I'm such a happy camper.

That's great! I'm glad it sorted itself out, because every analysis I could do pointed at it being some kind of server glitch.

I'll have to keep an eye out for it and hope the issue doesn't come up again in the future.

Tested with xial:
ljArchive Error: Error logging in: CookComputing.XmlRpc.XmlRpcTypeMismatchException: response contains struct value with missing non-optional member: fastserver [response : struct mapped to type LoginResponse]
at CookComputing.XmlRpc.XmlRpcSerializer.ReportMissingMembers(Type valueType, Hashtable names, ParseStack parseStack)
at CookComputing.XmlRpc.XmlRpcSerializer.ParseStruct(XmlNode node, Type valueType, ParseStack parseStack, MappingAction mappingAction)
at CookComputing.XmlRpc.XmlRpcSerializer.ParseValue(XmlNode node, Type ValueType, ParseStack parseStack, MappingAction mappingAction, Type& ParsedType, Type& ParsedArrayType)
at CookComputing.XmlRpc.XmlRpcSerializer.ParseValue(XmlNode node, Type ValueType, ParseStack parseStack, MappingAction mappingAction)
at CookComputing.XmlRpc.XmlRpcSerializer.DeserializeResponse(TextReader trdr, Type returnType)
at CookComputing.XmlRpc.XmlRpcClientProtocol.ReadResponse(XmlRpcRequest req, WebResponse webResp, Stream respStm, Type returnType)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, String methodName, Object[] parameters)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(String MethodName, Object[] Parameters)
at XmlRpcProxydee4c5a7-0236-45f2-82c7-9d2c80e68864.Login(LoginParams )
at EF.ljArchive.Business.Sync.GoThread()

Wondering if you're checking for and handling passwords with non-alphanumeric characters.

Tested with _rye:
ljArchive Error: Error logging in: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, String methodName, Object[] parameters)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(String MethodName, Object[] Parameters)
at XmlRpcProxy6c4b3e82-de18-497e-94c4-6099cb199972.Login(LoginParams )
at EF.ljArchive.Business.Sync.GoThread()

Same question for usernames.

hi xial,

Thanks for the error reports.

The first exception has been addressed in the upcoming release.

The second exception is a result of not being able to reach the livejournal server. You may have tried to connect during one of the times they were down. So you may want to try again.

The next release will include errors that make sense to the user.

After following wizard, got this:

System.ArgumentException: Column 'UserName' does not belong to table Comments.
at System.Data.DataColumnCollection.Remove(String name)
at EF.ljArchive.UI.Explorer.SaveJournal(String path)
at EF.ljArchive.UI.Explorer.FinishUpdate(Boolean success, Boolean cancel)

Hi The Cheat,

This has been fixed in the upcoming release, which should be available in about a week's time.