Good Reads Migration Finished!

Posted by Cyn | Posted in Family, Geekery, Health, Reading, RPGs | Posted on 17-08-2008

0

That was not pain­less at all. The import fea­ture is tetchy, at best. I had to go through the entire list of 1300+ books and fix their “book­shelf” assign­ments, and add some that just did­n’t import at all. I had over 1400 books in Now Read­ing, and I haven’t quite fig­ured out why there are few­er books in Good Reads. Oh well. It’s pret­ty much done!

The dates I’d read books, my rat­ings, and my reviews did NOT trans­fer to Good Reads, which is high­ly annoy­ing.

I was able to go through and update a bunch of books that I’ve read since NR stopped work­ing, and use the to-read cat­e­go­ry to request books from the library. As a result, there are 33 books await­ing pick­up now, and anoth­er 61 pend­ing (most­ly books that are real­ly new or not yet avail­able). That does­n’t include the inter-library loan items I request­ed.1

Sam and I had bonus gam­ing time tonight. He’s stor­ing up brown­ie points before Dragon*Con. Katie, unfor­tu­nate­ly, could­n’t sleep last night, then slept all day until about 11:30. Now she’s re-hydrat­ing and get­ting some food now. I hope she can go back to sleep. She’s def­i­nite­ly hav­ing a fibro flare. 🙁


1 I’m so tick­led that the library added a way to put in ILL requests online!

Grrr

Posted by Cyn | Posted in Blogging | Posted on 15-07-2008

0

The lat­est ver­sion of Word­Press is out, so I upgrad­ed this blog right away, as I usu­al­ly do. Of course, the plu­g­in I use most, Now Read­ing, choked and won’t work any more.

Le sigh.

The prob­lems with the pre­vi­ous “new” WP ver­sion were nev­er tru­ly resolved, and now the author’s forum isn’t work­ing, either. I fig­ure he has an actu­al pay­ing job, so I can’t fuss too much. But I’m still dis­ap­point­ed.

Amazon Weirdness

Posted by Cyn | Posted in Geekery, Reading | Posted on 14-06-2008

2

I’m tired. I spent entire­ly too much time over the last 48 hours futz­ing with the library part of this site.

The soft­ware I use to cre­ate that, Now Read­ing, auto­mat­i­cal­ly pulls images of book cov­ers from Ama­zon when­ev­er I add a book to the library. Ama­zon auto­mat­i­cal­ly sets affil­i­ate links up that way, so they’ve already said they don’t mind (there are affil­i­ate links to them on every page, so they are get­ting their traf­fic). I don’t usu­al­ly hotlink to any­thing, but some com­pa­nies actu­al­ly pre­fer it.

For some rea­son, the images keep going away ran­dom­ly. Some are for old­er books, but some are for fair­ly new releas­es, too. Ama­zon still has an image on their pages, but the graph­ics have moved on their servers.

I know they’ve tried to get their affil­i­ates to use their dynam­i­cal­ly-gen­er­at­ed wid­gets, which would pre­sum­ably update them­selves when a file is moved. I don’t care. I want to link to spe­cif­ic items that I’ve read or want to read or want to talk about, not what­ev­er their algo­rithms decide to link to.

Now I get to go through all 600+ books in the library, find images for their cov­ers, save same to my serv­er, and update the library records.

Foo.

Gravatars and Plugins and WordPress, Oh My!

Posted by Cyn | Posted in Blogging, Geekery | Posted on 05-04-2008

8

Since Word­Press 2.5 has Gra­vatar sup­port, I’m attempt­ing to add Gra­vatars to my blog tem­plate. Unfor­tu­nate­ly, I just keep get­ting errors, or a the default “no Gra­vatars” image (even for com­ment authors who I know have Gra­vatars, like me). I’m cer­tain that the author of this tem­plate isn’t going to update it to include sup­port, because her web site and busi­ness are up for sale. She has­n’t ever respond­ed to ques­tions in the past, either, so I fig­ure it’s sil­ly to look for help there.

I tried on anoth­er tem­plate, with the same errors. I real­ly don’t want to switch themes again, because I could­n’t even start to remem­ber every­thing I’ve cus­tomized in this one, and I’d rather not do it all over again. I’m annoyed, though. If any­one can help me, I’d appre­ci­ate it!

Update: Squee! They’re work­ing now! The clue I need­ed was in a post at Weblog Tools Col­lec­tion. Now I can try updat­ing the oth­er blogs!

Oth­er­wise, Now Read­ing is work­ing now, thanks to help from the author. I’m thrilled, as it’s one of my favorite plug-ins. When I get Read­er­Ware set up for us again, I’ll try to fig­ure out a way to export data from it to NR.

Cys­tats is not work­ing, though. I did­n’t even real­ize that it was bro­ken at first, because the error only shows up for users who aren’t logged in. Odd­ly enough, it works on some blogs that are run­ning 2.5, but not this one. The author of that plug-in has­n’t respond­ed to my ques­tions, though. It might be due to a lan­guage bar­ri­er, as his blog is writ­ten in Ger­man. Now it’s work­ing again, as ran­dom­ly as it quit work­ing. Why? Who knows? If you see an error on the site at any time, please com­ment and let me know!

I just real­ized that Live­jour­nal Cross­post also died in the upgrade. For­tu­nate­ly, there’s a fix described in the issues board at the devel­op­ment site that should make it work again.

Now I get to go back and see how many posts did­n’t go to LJ, and try to fix that lit­tle omis­sion.

WordPress Upgrade Woes

Posted by Cyn | Posted in Blogging, Geekery | Posted on 30-03-2008

7

Ack! I upgrad­ed to the lat­est ver­sion of Word­Press (2.5) yes­ter­day, and now one of my favorite plug-ins (Now Read­ing) isn’t work­ing! You can see the books I’m read­ing at the moment over there in the side­bar, and I can get into the admin­is­tra­tive inter­face, but the library dis­play does­n’t work. Any of the actu­al book or author pages come up 404. Meep!

It isn’t just on this blog, either—Fibrant Liv­ing has the same prob­lem.

The WP admin­is­tra­tive inter­face has been com­plete­ly redesigned. I’m not sure what might have been changed behind the scenes, so I’m a lit­tle wor­ried about try­ing to go back to the pre­vi­ous ver­sion.

I’ve post­ed mes­sages in the plug-in author’s forum and bug track­er. I’m hop­ing to hear from him soon! Rob actu­al­ly respond­ed in the com­ments, and the new ver­sion resolved the prob­lem. Yay!