A couple of days ago I had an issue with F1 not working with Firefox. That seems to have been a temporary glitch.
Today, however, F1 has stopped working both for Safari and Firefox – it just clicks ineffectually, no error message (or action).
Is there any chance this has to do with the recent upgrade? I’m now dragging urls onto the icon, which is okay, but live by the F1 workflow.
Did you check EagleFiler’s log in the Console application? There may be errors shown there.
F1 glitch
I was trying off and on all day yesterday. Console captured a few errors:
9/8/09 5:14:21 PM EagleFiler[6376] .sdef error: Operation could not be completed. (NSXMLParserErrorDomain error 1549.)
9/8/09 5:14:21 PM EagleFiler[6376] line number: 2
9/8/09 5:14:21 PM EagleFiler[6376] .sdef error: Operation could not be completed. (NSXMLParserErrorDomain error 1549.)
**9/8/09 **9:25:33 PM efwebtool[7599] Continuing after cancelled loading of http:// …
9/8/09 5:14:21 PM EagleFiler[6376] line number:
[Possibly?] 2 9/8/09 6:33:02 PM firefox-bin[186] Cannot find factory 00000000-0000-0000-0000-000000000000
[This morning] 9/9/09 8:52:24 AM firefox-bin[186] Looked for URLs on the pasteboard, but found none.
Actually, I was curious about EagleFiler’s log, not the console log.
I don’t see relevant errors. Just launches and “duplicate record” stuff. Still, F1 is inoperable in both browsers.
I’m not talking about the Errors window in EagleFiler, but rather the EagleFiler.log file in Console.
Have you tried restarting your Mac?
Yes, I was looking at the EF log in Console.
I swore I restarted the mac yesterday to no avail, but it just fixed the problem. My iMac is acting very glitchy in general, so I suspect this isn’t EF-related and may recur. Thanks for the patient replies.