Coffee heat rising

The Complete Writer…Completely Crazy-Making Writer?

This week’s serial installment of The Complete Writer — chapter 17 — is online at Plain & Simple Press. In today’s suspense-filled story, we navigate the perils of libel, defamation, and slander as we cling to the tight-rope of fact-checking.

Hand-over-hand across the Gorge of Electronic Peril…

This week, too, Ella finally gets it on with Lohkeh and a twit whines about his coworker injecting himself with insulin.

Friday is always Hell Central in the serialization department. For some reason, WordPress hates…just HATES…that writing book. Every. Single. TIME I go to post a chapter of The Complete Writer, some effing snafu keeps me sitting there for-freaking-ever wrestling and banging and whacking with the damned computer.

Honest to God I do not know why this happens, but it has happened every goddamned Friday since Week 1. Every time I try to post a chapter in the accruing “book,” WordPress just doesn’t wanna do it. And every time it has some new, unique, unheard-of, clever way to not wanna do it. No two snafus have been exactly the same.

Often it will have something to do with building an internal link from the table of contents to the chapter of the week.

Understand: there’s nothing very difficult about an internal link. Let’s say you want your reader to be able to click on the title to chapter 10 and be taken down the page to lovely chapter 10. Let’s say, for simple lunacy’s sake, that we have titled said passage in the magnum opus “Chapter 10.”

So you type the passage’s title, in the “text” mode, embraced and resting within a wee bit of code:

<h2 id=”chap10″><span style=”color: #0000ff;”>Chapter 10</span></h2>

This should cause your chapter title to look approximately like this:

Chapter 10

Dramatic, eh?

Well, “id=chap10” tells WordPress that the squib “chapt10” can be linked to. So back at your table of contents, you highlight Chapter 10, go ⌘k (or, if you prefer, point and click on the link icon), and enter…

#chap10

This link will then take the inquiring reader to the coded copy that reads Chapter 10.

How hard is this?

Extremely, if you believe WordPress’s antic of the day.

Among many evasive tactics, when you hit “update” on the page to publish the new data, it deletes the code around the chapter title. So the link in the TofC goes dead.

After 90 minutes of fucking with this, I finally gave up and sent it off to Grayson (guru par excellence) to figure out. No doubt he’ll have an explanation for why it can’t be done. Possibly I’ve maxed the number of internal links you can put in a single WP page? Who knows…

WhatEVER…I damn near lost my mind trying to make WP perform this very simple trick. It has done it before (true: unhappily) in the TCW page. It does it without arguing in the pages for Ella’s Story and If You’d Asked. But it just ain’t a-gonna do it today.

So I’ve gotten virtually nothing else done today.

Well. That’s not entirely true. Inventory:

Walked dogs 1 mile
Watered desert willow tree in front that Luis says is suffering from drought (a trick, what with the stupid springy hose I bought, which has to be secured to a tree limb so it doesn’t rewind itself back to the damn faucet)
Pulled out dead flowers in front courtyard; planted new flowers
Fertilized the paloverde tree and three citrus
Presently pouring the state’s entire allotment of Colorado River water to those, to soak fertilizer in
Cooked a package of pork; ground that with precooked chicken and veggies and mixed up a week’s worth of dog food
Watered potted plants in back
Swam in pool; ascertained that (thank god) it doesn’t need to be cleaned today, or at least not this minute
Inspected workman activity down the street
Soaked toes in tea tree oil
Posted two links to articles in The Economist for homeowners at NextDoor, re: ongoing discussion of homeless drug addicts
And miscellaneous stuff

And do I feel like working now? Hell, no!

FeedBurner in; Feedburner out

Very nice. I got FeedBurner ensconced on FaM, having discovered an error in the HTML snippet’s code and having persuaded a friendly IT guru to fix it, with sterling results.

Further observation, however, left the Beloved Proprietor of this website wondering. First, it became clear that the vaunted statistics we were to enjoy applied (duh!) only to those who elected to opt viewing the site in favor of having posts delivered to them by e-mail. Second, it quickly became clear that widespread complaints to the effect that stats were in error are probably correct.

Why, the Royal We asked Ourself, why are We doing this? The answer was simple: We don’t know. WordPress’s stats a) provide everything FaM needs to know and b) actually work, without requiring that one navigate to a different site. So, we decided to delete the Feedburner site, here and at The Copyeditor’s Desk.

The Copyeditor’s Desk, btw, now has its own domain name and concommitant URL: thecopyeditorsdesk.com.

Please feel free to subscribe to either or both(!), using your own choice of RSS feeds.

DANCE TO SPRING! (well…late summer)


A rose for WordPress

Funny is now officially part of WordPress! Hooorayyyy!

It was a project, because I haven’t the faintest idea what I’m doing, but the excellentsupport staff here at WordPress managed, with great patience and elaborate effort at explaining things in words of one syllable, to help me move the domain name over here. Thank you, Anthony and Douglas!

So, welcome to Funny’s new home. I hope you like the design, which was cadged directly from one of WordPress’s templates.

I’m now going to start publishing content that I copied-&-pasted over from iWeb. The result is that many of you will get pinged by posts dating as far back as December 25. My apologies — if there’s a way to turn off the ping function, I haven’t figured it out.

Originally I thought I should start from the beginning and work forward. However, slapping posts over here one by one is a time-consuming process. After a while it became apparent that it would be better to work backward from the present. As of now, I’ve got August and part of July uploaded, plus December and January. In the evenings while I’m sitting in front of the idiot box, I will keep moving copy, and so every now and again more outdated pings will go out. Sorreeee! 😳

Today being a workday, I must spend the next few hours editing feminist tracts. However, later today or tomorrow I’ll try to get FeedBurner onto the site. Be patient! It takes me a while to figure these things out.

What’s going on here?

Funny about MoneyatiWeb is down for the count, the Mac presently residing in Apple’s ICU. I’ve been planning to migrate funny to WordPress for a while, anyway, so this little headache presents an opportunity to get moving on that project.

It’s huge, and I’m still not convinced I want to do it. The amount of work involved is daunting–just capturing most (but not all) of the posts from the Net into Word takes about an hour for each month’s worth, and Funny has been around for seven months. Once I have the copy out of the Macintosh, it still has to be stripped of all the weird Microsoft tags and reformatted for republication. Augh!

Then I have to figure out how to migrate the domain name to WordPress, a complicated-sounding process,and then pay for the privilege, one that was included in the cost of .Mac. I wonder if this is worth the effort.

WordPress has some huge advantages, foremost among them that it’s accessible from any platform. With iWeb you have to be on a Mac, a killer of a restriction, since I can’t afford to own more than one Mac. Then you have to set up the Mac so that iWeb will access your site, and that is something I have no idea how to accomplish.

On the other hand,inserting graphics in an iWeb page is extremely easy, which can’t be said of WordPress; there’s no problem with pasting copy from Word into iWeb; and you can design your own page without having to know CSS. WordPress wishes to charge you if you put ads on your site; there’s no charge for that at Apple. While Apple charges for the use of its servers, in addition to space for your website you also can back up your data there. Alotof data. Taken together, all those are almost as big as the accessibility issue. Bigger, maybe… I don’t much care for the WordPress template I’ve selected, but I don’t see anything else that makes me happier. Plus–speaking of access–you don’t have to memorize passwords to get into your iWeb pages.

So the decision is not yet taken. If the Mac can’t be fixed, obviously I’ll have to go to WordPress. But if it comes back up…well. This is certainlynotthe path of least resistance.

More on Mac

Pete visited yesterday and left a comment on “MacHeadache,” apparently in the wee hours of Tuesday morning (hard to tell, since iWeb has come unstuck in time…it no longer knows what time it really is). I started to respond to his, which only just appeared, in a comment of my own and then realized I was going on at enough length to create a new post.

Here’s what Pete observed:

It does seem supremely lame that Apple migrated you to MobileMe without being sure you had a system that was compatible. I don’t know if .Mac is (was) technically aware on an ongoing basis what version of Mac OS you use, but it stands to reason, and they could have been smart enough not to migrate anyone who would break without warning. I’m not sure what the alternative would be, but they could at least have given you a chance to migrate elsewhere if you needed to.

But the rest of this stuff? Having a computer is just about the opposite of simplicity and frugality. In fact, to achieve anything resembling computing peace of mind, simplicity and frugality need to go right out the window. Here are a couple of examples:

Broadband would make those system updates download in a reasonable amount of time. Windows wouldn’t be any better in this respect. For that matter, neither would Linux. All the major operating systems are pushing big updates out to the installed base on a regular basis.

Panther is two major versions of the operating system behind. I realize you’re not the sort who gets jollies from a computer for its own sake, and that’s fine, but in general you would experience fewer crises of this magnitude if you were to keep up with the Joneses. Running Panther today is like running Windows 2000.

As far as iWeb goes, well, given that you’re aware of its limitations, I’m not sure why you torture yourself with it when there are so many free blog publishing solutions out there on the web

My response:

Functionality! Pete, yours is the first comment that has posted in over a week. Yesterday, if you had hit the “Add Comments” link, you would have seen an ad for MobileMe

I downloaded all the most current software, for which I had to pay at a time that was WILDLY inconvenient for me. Even though the Apple store’s manager gave me a 50% discount (turns out that’s fairly common-others have had the same experience), it still put my budget, which had barely recovered from the staggering expense of caring for a dying pet, back in the red. Eventually I would have bought the most recent OS, but when I could afford it, not when Apple ordered me to.

Yes, I know DSL is slower than broadband. I can’t afford broadband. In these parts it’s expensive, and I work for a university…by definition that means you don’t earn much unless you’re a football coach, a full bull in business or engineering, or an upper-level administrator. The cheapest cell phone I could get from Qwest — which I subscribed to only because pay phones are a thing of the past and I have to commute on a freeway that takes me a long, long way from home and from the car mechanic — is a stretch for me. I miss having a phone bill that is not a stinging hit each month.

All the rest of my software is up-to-date. The package that includes iWeb, called iLife, is the 2008 edition. I have followed all of the instructions sent by Apple’s support team. My son, who is a great deal more techie than I am, has also tried to make the system work. So far, nothing has succeeded

That you were able to post a comment suggests some functionality may be returning. However, it remains true that iWeb, while it has some attractive features, doesn’t have the interesting features supported by WordPress. I should be able to enter a StumbleUpon button, I should be able to subscribe to Feedburner, I should be able to register with Technorati, I should be able to register with Google, I should be able to ping other blogs. None of these things appear to be possible with iWeb.

I started Funny about Money in iWeb because I had never done a blog before and I doubted much would come of this one. Apple touted its user-friendly simplicity, and it looked like a way to play at blogging without having to put out much effort. I was already paying for Mac.com, which provided an extra e-mail account and which alleged (wrongly, I’m now told) to provide off-site storage space for Quicken backups. Since I didn’t expect Funny would go anywhere, I figured it wasn’t worth the learning curve involved in developing a website on more serious blogging software.

Now I figure Funny does have the potential to draw readers, and it’s kind of taken on a proverbial life of its own. Had I known it could be even mildly successful, I would have started the blog in WordPress, following Jim’s very cogent advice at Blueprint for Financial Prosperity.

It’s way past time to move Funny to WordPress. It’s going to lose most of its archive, but frankly, little of that is worth storing for the electronic ages. I’ll migrate the key posts first and then the ones I think are the best I’ve done so far. With any luck, once I get the blog on the new platform it will be even better and will have more opportunities to find new readers.

LOL! Yes, computers are the opposite of simplicity and frugality! But they are a part of our daily life. Just as you can’t get by without a cell phone, you can’t live a fully engaged life in America (or the world) today without a computer system and an online connection. It’s just the way things are.

Update: Blog migration project

Between you and me and the lamp-post, I spent most of yesterday fiddling with computers instead of working for the taxpayer. The project to learn WordPress and move Funny over there is coming right along, and in theory I could claim it’s sorta like work, because my EA (editorial assistant, a.k.a. her Sanchita Panza to my Doña Quixote) and I have conceived the idea of creating a blog for our office on the university’s intranet, which happens to use…yes! WordPress! So it’s all stewing together in the same pot

Worked…played…whatever I was doing until after midnight; then up at 5:00 a.m. for the usual round of chores and racing out the door. Labored like Sancho’s mule! But I learned a lot, figured out which posts to copy into WordPress, learned how to insert images (not as easy as it looks), found out some strange things, learned some HTML code (d’you know how long it’s been since I took an HTML class and decided I just didn’t want to know that?), and actually read an entire learned article on feminist epistemology for Our Beloved Employer.

WordPress is so, soooo different from iWeb. If only all the kewl things about each could be amalgamated into one fantastic blogging program. It is, for example, extremely cool that in iWeb you can drag & drop or copy-and-paste Sancho there into your page and he will appear online as he appears in iWeb. But it is also extremely cool that in WordPress you can type in a caption and voilà! the cutline appears below the image, unlike the one I just built in a textbox, which could appear…oh, just about anywhere on this page. We shall see after I (don’t) post it to the Web.

How kewl is it, though, that WordPress works with LaTex? OMG!!!

Apple sent out a groveling e-mail to its paying customers, promising that things are now so much better. Dollahs to donuts when I hit publish I will again be told that iWeb failed to publish, and again a visible but static page will appear online

The new young guru in my building at GDU, BTW, is an Apple acolyte (is that an Applyte?). He was surprised that I had managed to change the language for my Dell laptop’s log-in routine to Arabic. I suggested it was a terrorist plot to blow up GDU’s president, the Raven. He said, “Nevermore!” After some fretting around, we figured out the best way to approach the Arabic invasion was to crash the system, duck for cover, and then reboot. It worked. One shock treatment and Dell speaks English again.

At any rate, the kid couldn’t understand why I would feel any sense of dismay toward the beloved Apple. I offered to pay him to untangle the mess MobileMe has made of my system. He ducked for cover again

In another few days, I hope to complete the iWeb-to-Wordpress migration. Annoyingly enough, our office is getting some work in-house, dead of summer or no, and on the side I’ve fallen behind on a client’s project, so I will be reduced to working for pay. But as soon as the switchover is done, you should be able (I hope) to access it at a funny-about-money.com URL. I do hope.