Posting to WordPress from the Desktop

Filed Under Tools | 2008-11-21, 16:55

I’ve caved and finally started seriously looking at a desktop level application to manage all my blog posting. When you have as many sites as I do, it’s much easier (and faster) to keep them all in one interface. Having a web interface is nice for flexibility, but it is definitely slower.

Right now I’m playing with MarsEdit, which seems to do just about everything I want. There are a few things I’d change if I were the developer (I don’t like having to go to the menu to set the post date on a post I want to go live in the future), but overall I’m happy so far. Hopefully this will help me write even more each day across the different sites. I’ve already pumped out 3-4 blog posts for Geeky Tattoos in no time. So far the only major issues I’ve found are:

Resized Images
I like to upload full sized images to wordpress and then used the automatically generated thumbnail in my post. MarsEdit uploads the full image and then includes the full version in your post. It’d be nice to have this full functionality from the desktop, rather than having to login and tweak the post later.

Twitter Tools
It doesn’t seem to play well with the Twitter Tools plugin for WordPress. Posts are not getting saved with the checkbox that says “Notify Twitter about this post?” I’m guessing I’ll have to either edit the Twitter Tools plugin and figure out how to fix that, or just modify the database so that the default for this option in new posts is set to true. Luckily it fails in the right direction (i.e. not tweeting as opposed to constant tweeting).

Anyone else have any other tools they recommend for blog publishing? I’m primarily using WordPress blogs, so that’s a requirement. OS X is also kind of a requirement since I’m still using the Macbook Pro, but Windows based suggestions might be useful to others.

4 Comments



What the heck are you doing Spotlight?

Filed Under Apple | 2008-04-20, 14:52

I don’t use Spotlight at all thanks to Quicksilver. But I’ve noticed in my system.log that I’m getting the following messages over and over again:

Apr 20 14:44:40 egads com.apple.launchd[102] (com.apple.Spotlight[4906]): posix_spawnp(“/System/Library/CoreServices/Spotlight.app/Contents/MacOS/Spotlight”, …): No such file or directory
Apr 20 14:44:40 egads com.apple.launchd[102] (com.apple.Spotlight[4906]): Exited with exit code: 1

Anyone have any idea what’s happening here? I looked at “/System/Library/CoreServices/Spotlight.app/Contents/MacOS/Spotlight” and it has no size, so I’m guessing it’s leftover from something? Anyone have any insight?

Update:
hmmm weird.. When I check the file through a console I have:
sh-3.2# pwd
/System/Library/CoreServices/Spotlight.app/Contents/MacOS
sh-3.2# ls -l
total 1384
-rwxr-xr-x 1 root wheel 704720 Feb 5 22:30 Spotlight

But if I browse to it in the Finder, I see Spotlight (I’m assuming that’s Spotlight.app) with a zero KB size. If I try to open it it says it’s not supported in this architecture.

So confused.

SOLVED! Kudos go to Justin for hooking me up with the full copy of Spotlight.app. I backed up the old (apparently corrupt) one and the copied the new Spotlight.app from him into /System/Library/CoreServices. So far, so good and no more errors in system.log. Woohoo!

13 Comments



Full Screen Firefox and Safari on OS X

Filed Under Apple | 2008-04-11, 20:51

Maxmize to full screen on OS X

Anyone that has talked to me about what I don’t like about OS X has heard me complain about the inability to maximize an application to take up the entire screen in one easy step. Sure you can drag the corner out, but that’s an annoying “work-around” in my opinion. But thanks to Todd Dailey I have a more acceptable work-around for Firefox and Safari at least.

All you do is add a Bookmark to the Bookmark Toolbar (commonly called a Bookmarklet) that has this snippet of JavaScript instead of the URL that normally goes there:
javascript:window.resizeTo(1440,900);

Of course you’ll want to set the values to the same size as your screen resolution. You can check your screen resolution in System Preferences -> Display. And on Safari you can make it even simpler if you make this bookmarklet the first one in the list. Then you can just hit Command+1 and have a full screen web browser instantly.

This is also handy for web developers on all platforms. Want to see what your site looks like at 800×600, 1024×768, etc.? Make a toolbar button for each resolution! Quick and easy site previews while you’re working on pages.

18 Comments



coreaudiod and mdworker (aka Spotlight) crashing! Help!

Filed Under Apple | 2008-03-17, 00:22

Sad Macbook Pro

UPDATE: Apparently you just need to make a post on your blog and then suddenly the answer appears (or things start working right. mdworker decided to stop crashing all of a sudden, but just to be on the safe side I went ahead and rebuilt the launch services database at the suggestion of a friend with the following command in Terminal:

sudo /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user

As for the coreaudiod problem, I think I may have found the culprit. Awhile back I had installed some webcam drivers from IOXperts because I wanted to get my Logitech Orbit webcam working since the iSight doesn’t pan and tilt. :) Things just didn’t work and the IOXperts webcam drivers kept saying a camera wasn’t plugged in. I gave up at that point but left the drivers installed. As I was troubleshooting the sound issue tonight I found a way to reproduce it reliably. Going into the System Preferences -> Sound and double clicking sounds to preview them reliably crashed coreaudiod. I downloaded and ran IOXperts uninstaller and uninstalled all their drivers, and then sounds magically started working again. Again, so far so good. Hopefully these problems are fixed for good. I’ll leave the original post below in case any poor souls run into the same things…..

——

I’m frustrated with OS X on my Macbook Pro right now. It’s supposed to “just work”, instead I’m getting my audio randomly cutting out and apparently Spotlight is broken, and I haven’t even had this thing for 2 months. Anyone have any ideas? Google results aren’t pulling up much that’s helpful other than “reinstall” basically.

I haven’t had time to even get used to how everything interacts within OS X, so it’s tough for me to troubleshoot things. Hopefully someone out there might have some insight, or maybe I’ll have some luck at the Apple store with the Genius Bar. Here are the errors I’m seeing in Console:

3/17/08 12:06:26 AM com.apple.launchd[1] (0x10bc20.mdworker[831]) Exited abnormally: Segmentation fault
3/17/08 12:06:29 AM com.apple.launchd[1] (com.apple.audio.coreaudiod[125]) Exited abnormally: Segmentation fault
3/17/08 12:06:32 AM com.apple.launchd[1] (0x10bc20.mdworker[833]) Exited abnormally: Segmentation fault
3/17/08 12:06:38 AM com.apple.launchd[1] (0x10bc20.mdworker[840]) Exited abnormally: Segmentation fault
3/17/08 12:06:44 AM com.apple.launchd[1] (0x10bc20.mdworker[842]) Exited abnormally: Segmentation fault
3/17/08 12:06:49 AM com.apple.launchd[1] (0x10bc20.mdworker[844]) Exited abnormally: Segmentation fault
3/17/08 12:06:55 AM com.apple.launchd[1] (0x10bc20.mdworker[845]) Exited abnormally: Segmentation fault
3/17/08 12:07:01 AM com.apple.launchd[1] (0x10bc20.mdworker[847]) Exited abnormally: Segmentation fault
3/17/08 12:07:07 AM com.apple.launchd[1] (0x10bc20.mdworker[849]) Exited abnormally: Segmentation fault
3/17/08 12:07:13 AM com.apple.launchd[1] (0x10bc20.mdworker[851]) Exited abnormally: Segmentation fault
3/17/08 12:07:19 AM com.apple.launchd[1] (0x10bc20.mdworker[852]) Exited abnormally: Segmentation fault
3/17/08 12:07:24 AM com.apple.launchd[1] (0x10bc20.mdworker[854]) Exited abnormally: Segmentation fault
3/17/08 12:07:31 AM com.apple.launchd[1] (0x10bc20.mdworker[855]) Exited abnormally: Segmentation fault
3/17/08 12:07:37 AM com.apple.launchd[1] (0x10bc20.mdworker[857]) Exited abnormally: Segmentation fault
3/17/08 12:07:43 AM com.apple.launchd[1] (0x10bc20.mdworker[860]) Exited abnormally: Segmentation fault
3/17/08 12:07:49 AM com.apple.launchd[1] (0x10bc20.mdworker[862]) Exited abnormally: Segmentation fault
3/17/08 12:07:54 AM com.apple.launchd[1] (0x10bc20.mdworker[863]) Exited abnormally: Segmentation fault
3/17/08 12:08:00 AM com.apple.launchd[1] (0x10bc20.mdworker[865]) Exited abnormally: Segmentation fault

Here’s also the log file that got dumped:
Process: mdworker [908]

Read more

Leave a Comment