Thursday, January 10, 2008

Foxmarks 2.0.39 Released

We just released Foxmarks 2.0.39, a minor upgrade over 2.0.38 which fixes two bugs. We'd appreciate it if you'd download it and let us know if you see anything unexpected. This is our release candidate for AMO -- if no new problems crop up, we will likely make this available on the Mozilla Add-ons site (for a while at least) tomorrow.

Separately, we believe we have resolved nearly all of the server performance issues that have caused us all such grief. Those who have had problems with auto sync over the past few weeks should find that it now works much more reliably. Monday morning will be the next big test for us, but today was certainly the smoothest day since our launch in December; we are cautiously optimistic about the future. Thanks again to those of you who have had patience with us while we worked through these issues.

10 comments:

  1. Synch error when I synch from from Dell laptop and not from the Compaq. So it is not working properly. Tried to sync numerous times.

    ReplyDelete
  2. Synch error also on my mac g4 (Os X 10.4.11). The 2.x.x doesn't want to work on this machine. I tried to disinstall an reinstall Foxmarks but the synch error persists on this machine. The last upgrade to 2.0.39 doesn't solve the problem.
    On the other machines (1 mac G3 Os X 10.4.2 and 2 PC Xp) the 2.x.x releases works fine.

    Cheers

    Fortunato

    ReplyDelete
  3. Could y'all be more specific about your "sync error" reports? What does your foxmarks.log file say? Have you consulted the migration FAQ to see if maybe there's a fix for the problem?

    http://wiki.foxmarks.com/wiki/Foxmarks:_Foxmarks_Version_2_Upgrade_FAQ

    ReplyDelete
  4. So far so good. I think you may have finally hit the nail on the head with this release. I have not had one failure since installing it, not something I could say of the previous releases though it has been getting better. Thank you for persevering in getting this fully functional. I happily await a version that works with the Firefox betas.

    ReplyDelete
  5. :-) :-) :-)
    Finally also my last machine sinchronizes fine now (see my synch error post on January 11th, 2008 at 7:19 am). I disintalled firefox via AppDelete software and reinstalled a new copy. Now everything works.

    Fortunato

    ReplyDelete
  6. @Angel: That's a network error, usually due to automatic proxy detection (I think). Check out this page for help with that issue:

    http://wiki.foxmarks.com/wiki/Foxmarks:_Disabling_a_Proxy_Server

    ReplyDelete
  7. @ eric: That does the trick! Thanks.

    ReplyDelete
  8. @eric: It works!!! Thank You! :)

    ReplyDelete
  9. Ok - my error has occured since I upgraded my foxmarks
    what should I do?
    - Foxmarks/2.1.0.12 (/Places) starting sync with sync.foxmarks.com ------
    [2008-10-15 14:58:27] >>> POST http://sync.foxmarks.com/sync/bookmarks/getchanges
    [2008-10-15 14:58:27] >>> Body is: {"baserev":78,"log":{"mid":"fhf10tgk"}}
    [2008-10-15 14:58:27] >>> Callback(({username:"x", endrev:78, commands:[], toprev:78, continuous:true, baserev:78, status:0})
    [2008-10-15 14:58:27] Nothing to see here; move along.
    [2008-10-15 14:58:27] Success: Synchronization completed.
    [2008-10-15 15:59:11] ------ Foxmarks/2.5.0 (/Places) starting sync with sync.foxmarks.com ------
    [2008-10-15 15:59:12] >>> POST http://sync.foxmarks.com/sync/bookmarks/getchanges
    [2008-10-15 15:59:12] >>> Body is: (disabled)
    [2008-10-15 15:59:12] >>> Authenticating...
    [2008-10-15 15:59:12] >>> POST https://login.foxmarks.com/login/signtoken
    [2008-10-15 15:59:12] >>> Callback
    [2008-10-15 15:59:12] >>> POST http://sync.foxmarks.com/sync/bookmarks/getchanges
    [2008-10-15 15:59:12] >>> Body is: (disabled)
    [2008-10-15 15:59:12] network request failed; status is 804b0014

    ReplyDelete