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
If you’re a fan of ScribeFire and would like to promote it on your website, you can embed the widget below on your blog by clicking on the “Embed this Widget” link.
Scribefire
Embed this widget See full results for Scribefire
July 19th, 2009 at 6:43 pm
Thanks for the fix. I really appreciate it.
July 19th, 2009 at 7:28 pm
thax for that fix that’s make me comfortable
July 19th, 2009 at 10:07 pm
Totally appreciate all the work put into ScribeFire!
July 19th, 2009 at 10:50 pm
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: “0×8052000b (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..
July 20th, 2009 at 1:49 am
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:
—————-^
July 20th, 2009 at 1:50 am
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;" />
—————-^
July 20th, 2009 at 4:58 am
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).
July 20th, 2009 at 5:34 am
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?
July 20th, 2009 at 6:22 am
ERROR.
This shows:
July 20th, 2009 at 6:22 am
ERROR
“”
July 20th, 2009 at 6:25 am
the ERROR contains these commands:
“<hbox
"tab-monetize"
onclick="performancingUI.onLeftSidebarTabSelect(this)
July 20th, 2009 at 7:20 am
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;
————————-^ “
July 20th, 2009 at 8:35 am
@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).
July 20th, 2009 at 9:27 am
thank for this information
July 20th, 2009 at 5:48 pm
Thank you! Much appreciated..:) Keep up the great work \o/ .
July 21st, 2009 at 12:02 am
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.
July 23rd, 2009 at 4:40 pm
Thank you! iGracias! Danke! I appreciate your diligence and would like to report that I have had no error reports in any language!
July 26th, 2009 at 9:49 pm
Thank You For the UPDATE {http://PaulBrennan.ws}
July 30th, 2009 at 2:26 am
Dang da da dang dang dang… This is damn good software, yeeehaa!