Hello,
A quick question: a few of the feedly users are no longer able to use
their feedly command since they go upgraded to 0.2pre10. I am
personally not able to reproduce that problem. Is there a way to turn
ubiquity in debug mode and get more information about what happens
when we call addSubscribedFeed:
function installUbiquityCommands()
{
try
{
var url = getBaseUri() +
"content/app/ubiquity/commands.js"
var jsm = importModule(
"resource://ubiquity/modules/setup.js" )
jsm.UbiquitySetup.createServices().feedManager.addSubscribedFeed( {
url: url,
sourceUrl: url,
canAutoUpdate: true,
isBuiltIn: true
} );
$debug( "[ubiquity] successfully added feedly commands
to
ubiquity" );
}
catch( e )
{
$debug( "[ubiquity] failed to add feedly commands to
ubiquity
because: " + e.name + " -- " + e.message );
}
}
I am trying to see if there is an error preventing the commands from
being added/registered.
The symptoms the users are seeing is the commands being added (no
exception in the console) but typing fee in the ubiquity UI does not
list the feedly commands. If it can help, this is happening only with
a subset of users and I went back to prefixing all the feedly commands
to feedly- to make sure that there are no command name collisions.
Thank you
Edwin
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
