Ed's Blog

Links widget refused to show up.

earino — Fri, 04 Dec 2009 19:40:47 +0000

So, the links widget refused to show up in this wordpress blog. At first I thought that maybe there was something wrong with the theme I had picked. However, it’s an officially supported theme hosted on the freaking wordpress.com servers, so if the Links widget wasn’t working under *those* circumstances, then wordpress.com was doomed. It turns out that links (or even the stupid widget) won’t show up unless they are categorized. So, even though in the links widget it says “All Links”, it’s a stinking lie. Links have to have a category, otherwise they simply don’t show up. So, the images attached are:

The stupid links widget lying about showing all links
The stupid links widget showing a picked category (peeps in this case)
The “edit links” page, you can see that there are categories displayed
The “edit link” page, in which you can see how categories are added to a specific link.

To summarize:

If you are trying to get the links widget to show links in wordpress your problem is either:

You don’t have any links defined in the system

You haven’t actually enabled the links widget

Your links don’t have categories

Your category isn’t the one picked in the widget

My iPhone’s visual voicemail stopped working, so i fixed it.

earino — Thu, 03 Dec 2009 23:54:23 +0000

So, visual voicemail is one of the “features” of the iPhone. When I got my 3GS it was squirrely. At some point, it simply stopped working. I’m not really much of a complainer so I just dealt with it for a long time. I decided today was the day this problem went away. I would like to thank @spleck, @inflatedKarma, and @tma for their assistance on this project.

Changed my stupid voicemail password, thereby forcing the iPhone to stop just assuming “everything will be ok.” This is done by following the steps found on AT&T’s answer center. This is actually a pretty well written document, so I have to give props to AT&T for a job well done.
This didn’t make it work by itself. I attempted to then change my voicemail password on my iPhone to match as follows:
This didn’t work, so I had to reset all carrier settings. I had screencaps of that, but it seems I can only make 1 gallery per post on wordpress at my current wordpress skill level.
Once I did that, it asked me for my voicemail password. I set it appropriately and voila, I had visual voicemail.

I should be embarrassed it took me that long to get around to fixing my stupid voicemail. Now it works.

Quicksilver 57b hotkey not working

earino — Thu, 03 Dec 2009 02:41:32 +0000

If quicksilver 57 beta is not launching, and in the Console you are getting this error message:

12/2/09 3:26:35 PM    Quicksilver[10425]    HIToolbox: ignoring exception '-[SFResults count]: unrecognized selector sent to instance 0x1405a270' that raised inside Carbon event dispatch
(
 0   CoreFoundation                      0x95fbb40a __raiseError + 410
 1   libobjc.A.dylib                     0x96eeb509 objc_exception_throw + 56
 2   CoreFoundation                      0x9600790b -[NSObject(NSObject) doesNotRecognizeSelector:] + 187
 3   CoreFoundation                      0x95f62db6 ___forwarding___ + 950
 4   CoreFoundation                      0x95f62982 _CF_forwarding_prep_0 + 50
 5   QSInterface                         0x0018ee8c -[QSCollectingSearchObjectView objectValue] + 60
 6   QSInterface                         0x0019cd5a -[QSInterfaceController objectModified:] + 58
 7   Foundation                          0x966091c7 _nsnote_callback + 176
 8   CoreFoundation                      0x95f439a9 __CFXNotificationPost + 905
 9   CoreFoundation                      0x95f433da _CFXNotificationPostNotification + 186
 10  Foundation                          0x965fe094 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
 11  Foundation                          0x9660b471 -[NSNotificationCenter postNotificationName:object:] + 56
 12  QSCore                              0x001249da -[QSProcessMonitor addProcessWithDict:] + 218
 13  QSCore                              0x00124795 -[QSProcessMonitor appLaunched:] + 149
 14  Foundation                          0x966091c7 _nsnote_callback + 176
 15  CoreFoundation                      0x95f439a9 __CFXNotificationPost + 905
 16  CoreFoundation                      0x95f433da _CFXNotificationPostNotification + 186
 17  Foundation                          0x965fe094 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
 18  QSCore                              0x0012376e appChanged + 238
 19  HIToolbox                           0x97e42e29 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1567
 20  HIToolbox                           0x97e420f0 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 411
 21  HIToolbox                           0x97e41f4f SendEventToEventTargetWithOptions + 58
 22  HIToolbox                           0x97ed5e9c HIToolboxLSNotificationCallbackAllASNsFunc + 614
 23  LaunchServices                      0x912736e2 _ZL48LSScheduleNotificationReceiveMessageCallbackFuncP12__CFMachPortPvlS1_ + 232
 24  CoreFoundation                      0x95f2ab72 __CFMachPortPerform + 338
 25  CoreFoundation                      0x95f268db __CFRunLoopRun + 6523
 26  CoreFoundation                      0x95f24864 CFRunLoopRunSpecific + 452
 27  CoreFoundation                      0x95f24691 CFRunLoopRunInMode + 97
 28  HIToolbox                           0x97e6ff0c RunCurrentEventLoopInMode + 392
 29  HIToolbox                           0x97e6fcc3 ReceiveNextEventCommon + 354
 30  HIToolbox                           0x97e6fb48 BlockUntilNextEventMatchingListInMode + 81
 31  AppKit                              0x94dcfac5 _DPSNextEvent + 847
 32  AppKit                              0x94dcf306 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
 33  AppKit                              0x94d9149f -[NSApplication run] + 821
 34  AppKit                              0x94d89535 NSApplicationMain + 574
 35  Quicksilver                         0x0001ef30 main + 240
 36  Quicksilver                         0x00002fe6 start + 54
)

Go ahead and simply delete the ~/Library/Application Support/Quicksilver directory. That got it working. Based on other errors I saw, I believe I had picked a theme other than the default theme, and this was causing a problem. Realize that doing so will most likely remove any and all customizations you made. If you made customizations to quicksilver you probably already knew that.