The following changes were made to ScribeFire between versions 3.4.1 and 3.4.2:

Bug Fixes

  • Fixed security vulnerability in editor that could have led to an attacker gaining access to private data
  • Fixed issue with Zemanta data; data from Zemanta is now retrieved while the computer is idle

19 Responses to “What’s New in ScribeFire 3.4.2?”

  1. 1
    Hyun

    Thanks for the fix. I really appreciate it.

  2. 2
    Norvin

    thax for that fix that’s make me comfortable

  3. 3
    Anastasia Catryn Willwerth

    Totally appreciate all the work put into ScribeFire!

  4. 4
    aye

    Thanks for the updated but, the problem is still same. when i press F8 the scribe fire will open ‘n show dialog box : ScribeFire startup error: [Exception... "Component returned failure code: 0x8052000b (NS_ERROR_FILE_CORRUPTED) [mozIStorageService.openDatabase]” nsresult: “0x8052000b (NS_ERROR_FILE_CORRUPTED)” location: “JS frame :: chrome://scribefire/content/storage.js :: anonymous :: line 104″ data: no]

    No username ‘n password will create for this scribefire. what happened??
    please tell me………..??
    now, i’m using scribefire v2.2.10 ‘n it works!
    answer please…
    thanks..

  5. 5
    Antonio Liccardo

    At startup Sriefire 3.4.2 does not start in Firefox 3.5. Moreover I got this error clicking on preference (settings?) button:

    Errore interpretazione XML: entità non definita
    Indirizzo: chrome://scribefire/content/settings.xul
    Linea numero 47, colonna 3:

    —————-^

  6. 6
    Antonio Liccardo

    At startup Sriefire 3.4.2 does not start in Firefox 3.5. Moreover I got this error clicking on preference (settings?) button:

    Errore interpretazione XML: entità non definita
    Indirizzo: chrome://scribefire/content/settings.xul
    Linea numero 47, colonna 3:
    <checkbox preference="pref-display-auto-save" label="&performancing.settings.autoSave;&quot />
    —————-^

  7. 7
    Allen Davis

    aye,

    You might get better response if you open a user defect report at http://code.google.com/p/scribefire/issues/entry (or click the link in the sidebar to report a bug).

  8. 8
    serr8d

    With the last two or three iterations of ScribeFire, I have to hit PUBLISH twice. The first attempt just idles for some 40-60 seconds, with the ‘publishing’ graphic working away (like the hourglass, but not). I do nothing, or make changes; doesn’t matter. The second attempt always goes through immediately.

    Thoughts?

  9. 9
    David Rojas Elbirt

    ERROR.
    This shows:

  10. 10
    David Rojas Elbirt

    ERROR
    “”

  11. 11
    David Rojas Elbirt

    the ERROR contains these commands:
    “<hbox
    "tab-monetize"
    onclick="performancingUI.onLeftSidebarTabSelect(this)

  12. 12
    juacy willian

    erro na configuracao


    Erro no processamento de XML: entidade não definida
    Posição: chrome://scribefire/content/settings.xul
    Número da linha 85, coluna 26: &performancing.ftp.settingsMoved;
    ————————-^ “

  13. 13
    Vaughn

    @serr8d … Try clicking the blog name first to open the blog for viewing. I don’t know why, but this seems to reduce the instances of the posting freeze/fail thing you describe happening. (obviously I see this behavior too).

  14. 14
    usaha

    thank for this information

  15. 15
    janetleigh

    Thank you! Much appreciated..:) Keep up the great work \o/ .

  16. 16
    Anand

    This is one tool that has completely changed the way I blog. Infact I can now blog right from the spot that I find something interesting. :)

    Truly amazing.

  17. 17
    JulieDee the JayDreamer

    Thank you! iGracias! Danke! I appreciate your diligence and would like to report that I have had no error reports in any language!

  18. 18
    Paul

    Thank You For the UPDATE {http://PaulBrennan.ws}

  19. 19
    John

    Dang da da dang dang dang… This is damn good software, yeeehaa!

Leave a Reply