Since upgrading to 0.1.2 the only commands I have available are command-list, command-editor, and help. I tried restarting Firefox, which restored all my commands until I actually used one, then they all disappeared again.
- 1 Post
- 0 Reply Likes
same deal, downloaded the update to the latest firefox and no commands work, ctrl/space just bring up the black command box, i type, no short cuts hit, enter does nothing. not even "help" works
- 1 Post
- 0 Reply Likes
Yeah, happening to me too. It seems that the upgrade just un-subscribed all the commands, ad if I re-subscribe to them that work fine.
- 2 Posts
- 0 Reply Likes
- 3 Posts
- 0 Reply Likes
I believe I've had the same re-subscription same problem, so I switched back to 0.1.1. I assume that to do the re-subscription, one chooses "find new commands"? Before when I chose that command, I was getting a server error message, but now I get this:
"Sorry, the herd is currently being moved to a new location. Our apologies!
- Ubiquitous Management"
Since I haven't subscribed to "the herd", does that mean that I can't resubscribe to the commands?
"Sorry, the herd is currently being moved to a new location. Our apologies!
- Ubiquitous Management"
Since I haven't subscribed to "the herd", does that mean that I can't resubscribe to the commands?
- 25 Posts
- 4 Reply Likes
Well the built-in commands were moved to separate auto-subscribed feeds.
I believe the problemis that these feeds' sources are somehow pointed at wrong page - go to the about:ubiquity page and mose ove any [show auto-updated source] link for any of these default feeds. See the link? It will most probably end with ...html for you, while it should be .js
Possible fix:
go to about:ubiquity
scroll to where your feeds are
for each feed:
click on [view auto-updated source]
- a page should appear, if it's one line of text it's the problem we can solve
click "back" in your browser
click on the very same [view auto-updated source] link again
- if a javascript code (more lines than one) shows up, we're done
click "back" again and repeat for next feed
I believe the problemis that these feeds' sources are somehow pointed at wrong page - go to the about:ubiquity page and mose ove any [show auto-updated source] link for any of these default feeds. See the link? It will most probably end with ...html for you, while it should be .js
Possible fix:
go to about:ubiquity
scroll to where your feeds are
for each feed:
click on [view auto-updated source]
- a page should appear, if it's one line of text it's the problem we can solve
click "back" in your browser
click on the very same [view auto-updated source] link again
- if a javascript code (more lines than one) shows up, we're done
click "back" again and repeat for next feed
Abi, Employee
- 63 Posts
- 13 Reply Likes
Did any of you guys clear your private data/browsing history?
No, I have not cleared my history.
I only have this problem (commands disappear after one use until restart) on Mac, not on Windows.
I only have this problem (commands disappear after one use until restart) on Mac, not on Windows.
- 2 Posts
- 0 Reply Likes
I had not cleared my history, either, and I'm on Linux.
This doesn't happen every time, only once in a while... I can't figure out how to reproduce this.
Does this have anything to do with the Herd being down? Maybe the commands are trying to automatically update.
- 25 Posts
- 4 Reply Likes
Hey, I found one interesting thing.
I've got one feed in my command subscription list that is not auto-updated, and it has an "An update for this feed is available" link in the list now. When I click on that link however, instead of the correct JS code the source code of the command's HTML page shows. It looks like somehow code of the HTML page linking the JS file is used instead of the actual JS.
I can now imagine that since all the default commands are auto-updated feeds, when an update occurs the same happens and the HTML code is used where the command's JS code should, resulting in what I could observe - commands lost and HTML code showing when I click "view auto-updated source".
So my guess is that Ubiquity is using the referring HTML page's url instead of the command's JS URL when looking for auto-updates.
I've got one feed in my command subscription list that is not auto-updated, and it has an "An update for this feed is available" link in the list now. When I click on that link however, instead of the correct JS code the source code of the command's HTML page shows. It looks like somehow code of the HTML page linking the JS file is used instead of the actual JS.
I can now imagine that since all the default commands are auto-updated feeds, when an update occurs the same happens and the HTML code is used where the command's JS code should, resulting in what I could observe - commands lost and HTML code showing when I click "view auto-updated source".
So my guess is that Ubiquity is using the referring HTML page's url instead of the command's JS URL when looking for auto-updates.
Related Conversations
After update to 0.1.2, Google Search stopped being default action when no command has been typed beforehand
- Dawid Lorenz, 7 years ago
- Last reply: Fernando Takai, 6 years ago
- 10
- 3
- Problem
Ubiquity doesn't work after update to 0.1.2
- neu242, 7 years ago
- Last reply: achimbode, 6 years ago
- 24
- 32
- Problem
lost core commands after 0.5.4pre3 update
- ubi, 6 years ago
- Last reply: hlke, 6 years ago
- 2
- 3
- Question
- Answered
After update 0.1.2, "AltGr + Space" shortcut fails to work, yet worked with 0.1.1
- 2
- 0
- Problem
Related Categories
-
Ubiquity
- 829 Conversations
- 0 Followers





