Loading Profile...
Some verbs were not loaded as they are not compatible with Parser 2.
Ever since I upgraded to Ubiquity 0.5, I get a growl alert every time I open a Firefox window that says
Some verbs were not loaded as they are not compatible with Parser 2.
How can I fix this so I am not alerted, and ideally so that the error is nit occurring? I thought I could identify some offending subscription, but I have not been able to do that.
I'm on a macbook: OS 10.5.7, Firefox 3.5
Some verbs were not loaded as they are not compatible with Parser 2.
How can I fix this so I am not alerted, and ideally so that the error is nit occurring? I thought I could identify some offending subscription, but I have not been able to do that.
I'm on a macbook: OS 10.5.7, Firefox 3.5
I’m frustrated
10
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answers from the company
-
What version are you using? If you are using any of the 0.5pre versions, please make sure you subscribe to the release version of 0.5.
https://ubiquity.mozilla.com/xpi/0.5/ubiquity-0.5.xpi
If you are using the release version of 0.5, please try using the reset feature by typing about:ubiquity in the address bar (or running the help command) and clicking on the support tab. Please make sure to save any commands from the command editor and the URLs of third party feeds you are subscribed too first.
If one of these solutions works for you, let me know which once so I can track down the source of the problem.
4 people say
this answers the question
-
If you go to the command list ("show command list"), the commands that are not compatible with parser2 will have a strikethrough through them. You can then unsubscribe from those command feeds.
You will also get an error if you had user defined commands in the command editor that use the old API. If you created them using "create search command", delete them and remake them with the command again. If you wrote them yourself, you can follow this tutorial to update them to the new API.
3 people say
this answers the question
-
Inappropriate?If you go to the command list ("show command list"), the commands that are not compatible with parser2 will have a strikethrough through them. You can then unsubscribe from those command feeds.
You will also get an error if you had user defined commands in the command editor that use the old API. If you created them using "create search command", delete them and remake them with the command again. If you wrote them yourself, you can follow this tutorial to update them to the new API.
3 people say
this answers the question
-
Inappropriate?I found just one command with a strikethrough. It was "rotate page" from https://ubiquity.mozilla.com/standard.... I unsubscribed, and the error appears to be resolved. Thank you.
If https://ubiquity.mozilla.com/standard... is a native feed for Ubiquity, is it a bug that it has a command that is not supported?
I’m thankful
-
Inappropriate?Hmmm...thanks for letting me know about that Zeb. That command was moved to an optional feed, but for some reason it's not removing itself on upgrade. We'll work to fix that!
I’m thankful.
1 person says
this answers the question
-
Inappropriate?Today, the message returned. When I access the command list there are now many commands that have a strikethrough through them.1 Comment Add a comment
This answers the question
-
Same problem here! Most of the commands are not working. -
Inappropriate?I'm having this problem too, and I've already unsubscribed to the only command that uses the old API.
I’m grrrr
-
Inappropriate?I got the same problems starting today. The commands that don't work (OLD API):
From Mozilla Browser Commands
tab
close-tab
close-related-tabs
count-tabs
back
forward
zoom
tag
I seem to remember there being an undo-close-tab command here as well. It's gone now
From Mozilla Calendar Commands
add-to-calendar
check-calendar
From Mozilla Developer Commands
syntax-highlight
convert
escape-html-entities
From Mozilla Email Commands
email
last-email-from
get-email-address
From Mozilla General Utility Commands
word-count
link-to-wikipedia
calculate
gcalculate
sparkline
translate
create-bookmarklet-command-from
create-new-search-command
From Mozilla Image-Related Commands
rotate-page
From Mozilla Map Commands
map
map these
From Mozilla Social Networking Commands
twitter
tinyurl
share-on-delicious
rypple-ask
From Mozilla Web Search Commands
search
wikipedia
VideoSurf
yelp
weather
define
I’m missing my commands
-
Inappropriate?What version are you using? If you are using any of the 0.5pre versions, please make sure you subscribe to the release version of 0.5.
https://ubiquity.mozilla.com/xpi/0.5/ubiquity-0.5.xpi
If you are using the release version of 0.5, please try using the reset feature by typing about:ubiquity in the address bar (or running the help command) and clicking on the support tab. Please make sure to save any commands from the command editor and the URLs of third party feeds you are subscribed too first.
If one of these solutions works for you, let me know which once so I can track down the source of the problem.
4 people say
this answers the question
1 Comment Add a comment
This answers the question
-
Upgrading (though I was sure I was on the latest version) and resetting corrected this.
Thanks, Heather. -
1 person says
this answers the question
-
Inappropriate?I found the offending verb and unsubscribed, but I think that notification should only show up when you first start firefox, and not every time a new window opens.
1 Comment Add a comment
This answers the question
-
This behavior was improved in 0.5.2/3. We now only display that warning on startup.
-
Inappropriate?This error has returned with a vengeance on my FF. I have reset Ubiquity 4 times -- this is not resolving the issue.
When I go to look fo an offending verb, it looks like the majority of the verbs installed are incompatible! What's going on?
I’m frustrated
-
Inappropriate?Zeb, are you sure you are using the release version of Ubiquity 0.5? The offending verb should be listed in the command list with a strikethrough.
Latest release version: https://ubiquity.mozilla.com/xpi/0.5/ubiquity-0.5.xpi -
Inappropriate?jk3us - thanks for bringing that to our attention. I filed a bug and it should be fixed in the next maintenance release.
-
Inappropriate?Hi Heather, the link you provided to a new version does appear to resolve the issue :)
Note that updating via the extensions/add-ons window does *not* return an update available. So FF was telling there was no update available via the regular means of updating the extension.
I’m mildly disappointed.
-
Inappropriate?You will never auto update from pre to release though, because the "pre" is the beta branch. I'm not sure why you weren't updated to the latest pre version though. I'll look into what is going on.
I’m confused, as usual.
1 person says
this answers the question
-
Inappropriate?Hey. I don't know if this helps. Just installed Ubiquity (0.5.3) and then installed the bit.ly command. Every time I started Firefox I got the error mentioned. When I went to list ubiquity commands the bit.ly script was not shown (with or without a strike-thru). The only way to remove it was to reset Ubiquity.
I can replicate that many times over. It would be nice to have a warning when installing a script that its not compatible with the current version - I can install anything I want whether or not they work.
I’m slightly frustrated
2 Comments Add a comment
This answers the question
-
Jamie, that sounds like it may not simply be that that command was incompatible... sounds like there's another issue. Could you post the URL for that bit.ly script? I'd like to look into it.
-
Hi Michael. The Bitly one is here: http://mskadu.googlepages.com/bitly However I did just include that as an example - its happening with me with quite a few commands that I added - probably 80% I've tried from this page: https://wiki.mozilla.org/Labs/Ubiquit...
It could just be my installation for some reason. I have tried uninstalling and re-installing Ubiquity without any change. -
Inappropriate?Why do I want to subscribe to the new parser?
It adds support for alternate languages, but if I don't need, that, why would I upgrade?
about 30 of my UB extensions were 'incompat' w/new parser, so I just toggled off the new parser,
what am I losing?
I’m anxious,frustrated,sad,unhappy
EMPLOYEE
