Hmmmm.....hmmmm.

Yeah, esquifit is right, you can't see them in the command list
because they are outdated.  It's not a pretty way of handling it, and
there's no handy way to roll those changes back if you have auto-
update turned on.

To get rid of the error message, you want to go to the "Subscribed
Feeds" list on about:ubiquity.  There you will see the list of command
feeds you are subscribed to.  The feed in question is called "Ubiquity
cmds".

Heather

On Jul 24, 2:11 pm, esquifit <[email protected]> wrote:
> You probably has auto-update enabled for these feeds.  This has lead
> to the scripts having updated themselves to their latest version,
> which are actually for 0.5.  Since the new API is incompatible with
> 0.1.9, the commands are not recognized and consequently not installed,
> therefore you can't see them. AFAIK you have two options:
> 1) Uninstall the newest, incompatible version of these commands/feeds
> and install back the old version in case this is still available
> somewhere; in this case make sure you don't have the auto-update flag
> set.
> 2) Upgrade to 0.5.*
>
> On Fri, Jul 24, 2009 at 2:46 AM, Ben Babcock<[email protected]> wrote:
>
> > I'm running Ubiquity 0.1.9.  Starting today, I've been getting
> > Ubiquity notifications about the following commands: ping, tracert,
> > and whois.  The notification is always the same: the command is meant
> > for a newer version of Ubiquity, and it's suggested that I remove the
> > command.
>
> > Here's the catch ... when I go to the command list, none of those
> > commands appear to be installed.  I'm at a loss as to what's happening
> > here.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"ubiquity-firefox" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/ubiquity-firefox?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to