Well, there're two possiblities: 1. You uploaded your extension to addons.mozilla.org as well. In this case, Firefox will find updates to your extension once they're approved and up on AMO with its regular update check. 2. You included an "updateURL" (or similar, I forgot it's exact wording) tag in your install.rdf pointing to an URL that provides an RDF File which contains information about the latest release. You would need to update the RDF file and Firefox would query it wehnever its default update check occurs and find out about the latest version and the matching download path. If you didn't include an updateURL in your first version, I'd suggest you upload it to AMO. It also saves you from having to worry about all that RDF stuff. Although outdated, I think the "update" parts haven't changed: http://developer.mozilla.org/en/docs/Extension_Versioning%2C_Update_and_Compatibility Greetings xeen
On 7/15/07, Foreningen Selvet - Jesper Staun Hansen <[EMAIL PROTECTED]> wrote: > Hello > > I've been looking for this on newsgroups and mozilla developer related > site, but this seems like its "something everyone knows", but I dont :O > > Well, I've made my first release on the 6th named "heroes-0.1.xpi" and > then today named "heroes-0.2.xpi" and thrown them in downloads/, so far > so good. While I wait for the mirrors to update, then I would like to > hear how the client (firefox XULrunner update manager (at least thats > what I think its called)) finds out I made a new version. > > > Thanks in advance. > > _______________________________________________ > Project_owners mailing list > Project_owners@mozdev.org > http://mozdev.org/mailman/listinfo/project_owners > _______________________________________________ Project_owners mailing list Project_owners@mozdev.org http://mozdev.org/mailman/listinfo/project_owners
