The following bugs were fixed in PFF 1.1.1 beta 1
- Post as Draft now works ;)
- MSN Spaces Categories now work (you'll need to re-add your msn
spaces account) - Delicious now grabs the correct post for bookmarking, not the *last* see:
http://performancing.com/node/965 - Editing type now saves state (Between Rich and Source Edit)
- Preview window now shows URL as normal underlined urls
- Clicking on a link in Rich mode will no longer launch the url (only
in preview). - Hidden pref for encoding type. 'performancing.settings.defaults.encoding'
- Added performancing.com to the account manager
Please let us know if you have any issues with these fixes and report back!
Thank you everyone!













Any feedback?
So anyone tried the new beta? Any feedback?
We really need your comments, even if it is "all works fine for me", particularly if you blog in a language other than English as encodings are something we are finding tricky to test ourselves!
Maybe if we could find the download link...
Been going in circles on this web site for the last ½ hour and cannot find the link to the beta version anywhere, so it doesn't surprise me you aren't getting comments - can't comment on what you can't find.
I'm hoping the beta will fix the Atom error that pops up every time I try to post using Blogger.
All I do is fine with the beta ...
It looks good ... I don't experience problems.
Installation went good.
Well ... we'll see ... I just wanted to let you know that I am fine with the beta :-)
Beta download
michigantelephone, please follow the first link in the post above.
Yes, it is on there, but its
Yes, it is on there, but its not obvious :(
I just made it a bit more so.
You can get PFF 1.1.1 beta 1 right here aswell
@michingantelephone: Could
@michingantelephone:
Could you expend upon what problem you are getting with Blogger?
Thanks so much!
-Jed
The problem
Using either the release version or the beta version (which I just installed), when I click the "Publish To:" button I get an alert popup box (with warning triangle/exclamation point graphic) that says this:
There was a possible error contacting the ATOM server: Error #3: [object Object]
And the post does not get published. I can go to Blogger directly and publish it with no problem.
Note that if I click the "Publish To:" button multiple times, it seems I keep getting the error, but the Technorati tags get re-appended each time, so if it ever was successful I'd have to go in and edit out a bunch of duplicate Technorati tag lines.
I won't say that publishing has never been successful but far more often it doesn't go through and because of the Technorati tag issue I don't want to keep re-clicking to see if it will finally "take."
EDIT: Added February 8 - I made a few blog posts yesterday and on only one of them did it fail. I'm thinking that one of the following things may trigger this error:
Or maybe it's none of the above. All I know is that it's really frustrating when it happens.
Using 1.1.1 beta 1, I was
Using 1.1.1 beta 1, I was able to post drafts to wordpress.com. And it shows in "History" tab. But how do you retrieve previous drafts? Or drafts made on wordpress.com itself?
@ismangil, I don't think the
@ismangil, I don't think the API allows that.
Also, how far 'back' are your previous drafts? PFF currently only holds the last 10 posts made (including drafts).
I want to make it configurable to allow more, but there are some performance issues I need to work out first.
Jed, OK, no big problem. The
Jed,
OK, no big problem. The draft post, which is made on wp.com is definitely contained within the last 10 post. But as you already explained tha API is not there.
Compatibility with Squarespace
PFF has never worked with my Squarespace blog.
Protocol: metaWeblogAPI
URL: http://www.squarespace.com/do/process/external/PostInterceptor
There is no success or error message. The progress bar in PFF says "publishing" and then it just stops after a while.
Todd
Multi-Paragraph Formatting
If I hightlight several paragraphs on the page, then use the Context Menu->Performing->Blog this page, PFF splits the window and creates a new post. The problem is that PFF removes all the paragraph formatting and collapses all the text into a single paragraph. Obviously not the desired behavior. PFF should maintain the paragraph or line break formatting of the source page
@tweverett, Yes, we do not
@tweverett,
Yes, we do not support Squarespace yet, sorry :(
They seem to do something 'different' in their XMLRPC api, so we'll need to find out what and make the change to make it work with them.
@Mike, yes, when using 'blog this' we do not mainatin the formatting (however if you drag and drop we do), we will definitely need to fix that for 'Blog this'.
Trackbacks don't work
Although I enter the correct web links for trackbacks, I have yet to actually see one appear on the site I'm attempting to trackback to. But if I go to a standalone trackback generator and use the same URL, it works just fine, so it's clearly not that the site won't accept trackbacks. This has happened to me twice today - both times I entered the TrackBack URLs in the "Publishing Options" section, both times the post actually went through without the Atom error (thankfully!), but neither time did the Trackback get registered.
Is there any way you can actually display the Trackback response? This might help in diagnosing problems. By the way, I am using beta 2 at the moment.
Michigantelephone, Let me
Michigantelephone,
Let me look into that, and if I don't find anything I'll send you a build with trackback feedback (can you PM me your email address?)
Thanks
-Jed
Spelling
You guys aren't great spellers, since under TrackBack URLs, you've got (Comma seperated lists). In fact, since those first two words have become a single adjective, it should be Comma-separated. Better would be (Separate your items with commas).
Bloggers in general are abysmally bad spellers and barely aware of grammar ***sigh***
Anyway, I just used it in LiveJournal with Flock and I liked it much better than the DeepestSender version Flock offers. I don't yet understand all the features and options, but the interface is nicer and more intuitive for me.
I suppose you want feature requests elsewhere, but time is short so just to say I wish OnlyWire were integrated.
Cheers!
Post new comment