June 10, 2009
ScribeFire 3.4.1 Released
Filed under: Releases, ScribeFire -- Christopher Finke @ 07:49pmI just uploaded an update to ScribeFire 3.4, which unfortunately still had some debugging dialog boxes in it. Sorry for the inconvenience; the update will available in about an hour.
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
June 11th, 2009 at 11:07 am
There’s a behaviour I don’t want that started in 3.4, it tends to open a blank entry with in it.
June 11th, 2009 at 11:08 am
oh it missed out the code I pasted, it’s font face san serif and close font attribute twice.
June 12th, 2009 at 6:08 am
There is some error with the update, it wouldn’t install; something about an error with the hash value
June 12th, 2009 at 7:44 am
Update to that supposed problem, it seems to have been a download problem. Still the best blogging tool for FF users. Keep up the good work
June 17th, 2009 at 10:49 am
Hello Chris,
after the update I have the following problem: When writing a text the font and the font size change after some lines so that I must customize them before sending to my blog.
Do I make something wrong or is that a bug?
Best regards
Gerhard
June 21st, 2009 at 10:20 pm
latest ScribeFire add ons still having bugs, so i dont want use this. i use scribefire old version scribefire 2.2.9 its work!
for this 1-3 months i dont want update my scribefire untill it finished well.
thanks
June 22nd, 2009 at 5:44 am
Hi,
Thank you for your great addon
I have a problem with scribefire , I post codes to my weblog in the following format :
[php][/php] or
[plain][/plain]
but when I use scribefire to post codes , it changes some characters to html like and etc.
can you please fix this error ?
I want it to treat the text between [anything] [/anything] as a code and dont encode it to html.
June 23rd, 2009 at 9:45 am
I have a few nasty problems with 3.4.1 – I mainly use plain text editor.
1) It adds font face tag to an empty post and to any opened post every time it’s opened in plain text editor. I have particular styles in every blog and do not need that entry, have to remove it every time, why to add it?!
2) First time I press publish it adds two BR entries at the end and doesn’t actually publish anything, I have to press publish second time. Again, I don’t see reasons to add BR twice at the end automatically without asking me if I need that. Especially if that’s what’s causing the post to not being published from the first time!
3) It does seem to screw up special characters sometimes (didn’t text extensively, just had one occurence and one problem i.e. 100% on too small a ground so far), especially if switched between plain text and enhanced editor a couple of times. Previous versions handled this cleanly.
Please remove this new strange behaviours. “Even better” is the worst enemy of “Best”
June 23rd, 2009 at 9:47 am
Update: if I remove the double BR and press publish again, they are not added but the post is published second time. This happens to all 3 different blogs I have. Quite annoying to have to press it once, wait or sometimes forcefully close and then press Publish second time.
June 24th, 2009 at 12:47 pm
Every time I created a post, ScribeFire keeps adding a font face=sans-serif HTML tag to the content. Is there suppose to be something in SF that can disable this?
June 28th, 2009 at 12:31 pm
What is going on with Scribefire 3.4.1? I have 4 blogs at this, and scribefire mess up with the categories of all my 4 blogs. And, if i try to publish 2 posts, the second appers ‘null’ and i have to leave it….. The older version was ok for me.
June 29th, 2009 at 8:27 am
Thanks for providing this addon
But there’re some problems
1.I don’t need the code “” and where can I cancel it?
2.Every time I publish an article, it seems to become a scheduled article (or something like that). Then I need to republish it and be sure that the draft checkbox isn’t checked (Usually is checked). It’s weird that I don’t need those features.
Looking forward to the coming updates!
June 30th, 2009 at 1:54 pm
After a server upgrade, I now need to use SFTP to post rather than FTP. Does ScribeFire work with SFTP?
July 8th, 2009 at 6:01 pm
i hope ScribeFire can support ~ and support picasa like a soft named Zoundry Raven. it will be fun and easy. thx
July 9th, 2009 at 10:29 am
Major problem… everytime I try to log onto my scribefire, it tells me I have an error with my user/password…. what can I do to reset everything???
Please help!
July 10th, 2009 at 12:57 am
You seem to have added a lot of “fool-proof” things to the codes and this makes it very unusable for the people who mainly use the plain text editor to post for various reasons and created several problems which make it not that cool a tool like before and often I find myself forced to post from web because of it which kind of defeats the purpose.
Such as
1) automatic font face sans serif tag (added at each blank entry opening so that second time after closing all you already have it twice). Why on earth force it on people? May be they prefer serif! Or what is more likely they prefer the style set in their blog CSS, almost for sure!
2) automated transforming of lines in plain text from html or at posting – leads to any post sent from plain text editor NOT be posted the first time and catch a double BR at the end. Second time gets it posted even if we remove BR (I do not need to uncheck “drafts” like another user above, it’s always unchecked without my intervention in my post dialog).
Again, VERY unhandy, since if we need to control exactly what is sent to server and let it handle the rest, we need to post from this plain text viewer. This also preserves plain text line breaks if we later need to edit it (and it’s not always we can use ScribeFire for that), the one-line posts sent from HTML editor are not always quite handy to handle afterwards!
ALSO this makes us adding our own markup in plain text like say paragraphs NOT display correctly back to HTML like before but as transformed and added additional BR at every line break, while we sometimes need to break it our own way for various reasons. This is again VERY unhandy.
Someone who does not understand the code does not need the plain text editor, but someone who does and may need it, lost control of it with this automated two-way conversion. Please, return it back as it was? It was perfect. Please!
July 10th, 2009 at 1:06 am
I am sorry for posting again, I know I could swear I did it before, but could not see my comment from ScribeFire info tab, so I reinterated.
Then again I now understand better where the posting bug and editing inconveniences come from.
And I do thank you for your great job. I was actually about to go looking for “Donate” button on this site (which I did not find by the way) when this thing appeared and I’m afraid it will become actually unusable for me if this “forced automation” tendency continues.
August 5th, 2009 at 6:35 am
Hope this is a good place to say it. One of the continuing annoyances I have is that double-clicking on a word to highlight it in preparation of making a link also highlights the space following a word.
Can this be changed?
August 10th, 2009 at 4:57 am
is there a way to proof-read while using scribe fire ?
August 13th, 2009 at 6:18 am
Hi, I am devoted to scribefire, use it a lot. Maybe I have been sloppy with reading manuals and such, but I still would like to ask if there is a possibility to add some checkboxes with functions to the small window that comes up after I have pressed the publish-button. One checkbox for : OK (clear the editor) and one box for closing the scribefirewindow? If these are checked there would only be 1) choosing blog and category 2) publish 3) press enter. Possible?
August 16th, 2009 at 4:19 pm
ScribeFire is wonderful! Thanks. It makes blogging so much easier than using Blogger! I really appreciate your efforts.
August 27th, 2009 at 1:17 pm
I am very disturbed that every release you re-enable the tracking pixel. STOP PLEASE…
If I disable it, your update shouldn’t reset my change. None of my other settings are reset…
My annoyance is heightened because I have to go back and verify and update multiple posts MANUALLY to correct this. It ends up costing me more time to use this nice tool that is supposed to make things faster…
September 2nd, 2009 at 3:37 am
when ever I tick the box to post to delicious I get a javascript error telling me that I need my username and password but there is nowhere to enter it?
I’ve tried making sure that I’m logged into delicious before I post but I get the same thing?
what does it need to work?
September 13th, 2009 at 7:29 am
i cant remove the Post Timestamp Thing!!!
So All my Posts Get Scheduled And It pisses me Off O_O
September 30th, 2009 at 10:24 am
Hi,
Great tool… I switched over to using Linux, and now the scribefire I have is not saving passwords, it asks me every time I switch from one blog to another, for the the password… which more or less defeats most of the purpose for me as a convenience tool.
I’m hoping that I just need to tweak something, there are several things in the Linux Firefox which are a little different than the Windows version. If you could let me know where this tweak is that would be great.
Thanks again for taking the time to make this tool. It is very handy, for people like me who are posting to 10 – 12 different blogs every day.
October 6th, 2009 at 2:55 pm
You have a problem with encodings. I’ve just installed your extension to read/write to my blog and suddenly found encoding error. It will be great if you fix it.
Firefox 3.5
blog: dair-targ-one.livejournal.com
encoding: utf-8 (my blog actually written with cyrillic — but I think it’s easy to recognize encoding problems even with chines pages).
October 12th, 2009 at 11:53 am
Hello,
I’m getting hidden identity code of Zamanta, Would you please fix that problem. I’m using Scribefire but now it looks wired because I’ve to check each of my posts and have to delete the zamanta codes (blank space but looks so odd). I’m also looking a stable version of scribefire from you. Thanks for your great jobs and making blogging experiences more easier.
October 27th, 2009 at 3:33 pm
Now this looks pretty interesting. I wonder why I have not heard of you before.I’m going to check scribefire out. Sometimes wordpress just gets me overwhelmed.
October 29th, 2009 at 1:07 am
Just tried scribe fire, and am quite exited at getting this. Was hoping to get a couple of features too, like adding a flv upload button.
Also how do I get all my previous posts, and pages? The posts just lists about a handful, there is no paged navigation for the post list. I think I have about 50K posts and 15 pages on my blog.
By the way, when I tried to edit an already published post which had php code in the source format, got it all mixed up, and finally I removed the code from the wordpress admin page.
November 4th, 2009 at 2:40 pm
I have been using blogdesk but as it have limitations i have now switched to scribefire. Future ad dons like editing pictures would be nice like blogdesk but apart from that it makes my life easier as a developer and writing on the fly. Keep up the good work. Johan
November 17th, 2009 at 12:08 pm
This is a great add-on and i am going to write about it for my blog readers. Its doing great for me, its light and in the browser itself, this makes it the best.
November 18th, 2009 at 7:31 am
I´m trying to install at my notebook, but the link says there´s no server????? What´s wrong?
November 19th, 2009 at 1:26 pm
Hi!
I have a problem with encodings too (and again it’s cyrillic/utf-8). It was surprising to find such problem in so well-designed app. Hope you’ll fix it soon. You do a great job! Thanks
January 10th, 2010 at 9:46 am
Please, create a Google Chrome addon like for FireFox!