It’s only a flesh wound, lambchop!

Google has given V-I a clean bill of health.  I’ll slowly re-add the old content, but I have to do it carefully since I don’t know exactly where the nastiness was.  In the interest of getting things up and running, I basically blew up the old site, although I still have the database, which has all the old posts and comments.  Importing it a few posts at a time could be a challenge, but I’m sure someone out there has done it, so I just have to learn how.

For now, feel free to re-add new posts for the old topics if you’d like, and I’ll integrate the old content as I get to it.  If there’s something you’re dying to review from the old stuff, let me know in the comments here, and I’ll see what I can do!

I’ll take care of all the cool sidebar stuff we had today or tomorrow.  How do I know what I’m listening to if I don’t have Mitchell’s Recent Spins in the right column?

17 thoughts on “It’s only a flesh wound, lambchop!

  1. Comments about the new look:

    I like the long list of the recent comments. I think I prefer the older approach which listed the threads by the most recent comments, but only listed the the two most recent posts within an individual thread.

    Another idea: Just list threads, not the comments or name of person making the comment. (I sort of like seeing the person’s name, but I would be able to tell if a comment came on a thread…then again, not really, not without dates and times.)

    Another idea: What if you had the most recent comments list featured most prominently in the middle, with the new posts on the side? I’m not sure I’m sold on that idea, but I’ll throw it out there.

    Whatever the case may be I think the current UI is a little better than the one before it.

    Thanks for doing this!

  2. Yeah, the way we used to have the recent comments was some pretty nice code-grokking by a younger me. I can’t remember how much of it came with the plugin we used and how much was rolling up my sleeves and getting under the hood. Definitely near the top of my list, if for no reason other than to prove to myself I still can.

  3. Well, at least you proved you can do it! The comments seem busier though, but that’s being nitpicky.

    By the way, you know how there’s a button at the top for starting new posts? Can one be made to take me to all the posts, or just to the drafts? I often work on old drafts and if there were one button that could get me there, that would be cool.

    1. Reid, sorry I never answered your second question. When you’re in the dashboard, if you click “posts” in the left sidebar, you’ll be presented with all the posts you’re allowed to see, including drafts. from that page, you can click on “mine” just to see your posts, or you can click on “drafts” to see all the draft posts. Let me know if this doesn’t make sense. Additionally, you can click on any of those post headers to sort by that column. Click “date modified” to see the drafts (for example) in order beginning with most recent. Click “date modified” again, and it’ll sort in order beginning with least recent.

      It’s not the one-click option you suggest, but the functionality is already there and I’m not inclined to seeing if I can grok that. At least not until I get all our old content back up.


      1. Let me know if this doesn’t make sense.

        I think it does. This is the way I get to drafts now. I was just trying to decrease the number of steps needed to get there.

        Additionally, you can click on any of those post headers to sort by that column.

        What’s the post headers?

  4. No, that’s a different plugin from the one we used before, out of the box with no tweaking on my part. Yeah, there’s no way I’m leaving it like this. Those bullets are terrible.

  5. Yes. I’ve done it here several times.

    When you first look at this, you’re going to say you don’t want to do it because it’s too much trouble. But it’s not as bad as it looks. I’m giving you the basics. You can learn a few tricks later.

    Type this. I mean it. Type it verbatim. In a comment below.

    YOU DON’T HAVE TO SPACE THINGS LIKE THIS. The spacing is just there to make it easier to follow.

    This code displays this:

    Jill Smith 50
    Eve Jackson 94

    See how that works? If you want to add more rows, add another set of TR and /TR tags and in between, add more TD and /TD tags.

    In short: TR means TABLE ROW. TD means TABLE DATA. You can make as many rows as you want. You can make as many columns as you want, too, but at the basic level, you need to make the number of columns the same for the whole table.

    Give it a try in the comments here. Let me know if you have questions.

  6. By the way, I really like the nested reply feature in the threads.

    Also, is there a way to include more threads that have new post (in the right hand margin)? If not, or if it takes too much time, never mind.

  7. I never liked the nested comments, which is why I always had them turned off on VI, but I’ll leave them. They’re fine with me.

    I’m growing displeased with this template anyway. Wanna make changes, which is why I haven’t messed with either sidebar in a while. Thanks for the suggestions.

  8. I don’t always like nested replies, but I like them on this platform. They’re not ugly to look at or hard to read. I love the fact that you can reply on an older post, and that will move the thread to the top of the column (in the right hand margin).

  9. oooookay. after about two hours of trial and error, i figured out how to export the old posts from the old vi database and import them to the new one. if you click the category “v-i” in the left sidebar, you’ll see the original “merry christmas” post from 2003. i have turned off comments because i don’t want anyone messing with that post before i figure out how to do similarly with the comments for that post. it should be almost the same procedure but with a few extra steps, which will complicate things a little, but if i can pull it off, i’ll be able to import a large number of the old posts at one time, then a large number of the comments for those posts also all at one time.

    it was both easier and more difficult than i expected. weird.

    please disregard this: i’m writing it here as reference for myself.


    1. use sql query to narrow results to target posts
    2. select all results, export as csv (for now!)
    3. import csv to spreadsheet
    4. delete phased-out headers
    5. modify author id, post id, comment status, and that’s it (?)
    6. export from spreadsheet as csv
    7. import to mysql as csv
    8. manually add categories to posts
    9. ta-da!

    note to self, in case i don’t get to try it tonight (which i won’t). duplicate old vi dbase, modify the copy dbase (keep the original), export as sql, then import directly as sql. should work!

Leave a Reply

Your email address will not be published. Required fields are marked *