Oh man, they did it :-)
XML-RPC support for Textpattern 4.0.3 is here
And you can go to the new Download 4.0 XML-RPC page in order to get it and install it on any existing 4.0.3 Textpattern powered site.
[...]
Posted Jun 4, 01:56 pm by Pedro Palazón
Follow the links to get more info. Read the comments. Nothing much more to say yet. The function should be tested by Jed and everybody interested in using Performancing for Firefox with Textpattern.
Please leave comments about every interesting aspect of this breaking Texpattern news here!
Technorati Tags: Markus Merz, 2006, Textpattern, TXP, XML-RPC
powered by performancing firefox
WOW and some glitches ...
Installation of the Textpattern XML-RPC is absolutely easy
Do as described on the Textpattern page or use wget, tar and mv if SSH is available. Some first notes about Performancing for Firefox and posting with the brand new Textpattern XML-RPC API.
I used the MetaWeblogAPI and all sections are recognized immediately and listed as individual blogs with their names. No site name is shown which will create problems if you add more then one site with similar sections! I created a first post with PFF and checked/marked one category. All categories are shown in PFF on one level. So PFF does not show the nested structure of TXP categories.
Jed, please allow to configure blog naming! At least show the domain ...
Posting HTML to Textpattern with PFF works fine.
All CSS inline styles seem to work perfectly well. I.e. drag & drop of a picture and declaring it to be on the right creates a new div and the inline style moves the picture to the right without a problem. It is absolutely no problem to mix HTML and Textile markup (if posting as draft! / see explanation below) as PFF does not recognize/touch the Textile markup at all and the interpretation is done by Textpattern.
One glitch is that categories are not handed over to Textpattern by PFF. This might still be a bug in the Textpattern XML-RPC implementation of the MetaWeblogAPI.
Another worse glitch is the well known 'feature' in PFF about posting double br tags instead of paragraphs (p). This seems to be only the case when posting an article for the first time. The editing of existing articles works fine changing the section is no problem and PFF does not show that double br behavior again. But it still does not post p tags :-( Funny and still to be tested. Maybe it has to do with source code editor view and the WYSIWYG view.
Jed, please give an option to not touch the created source code at all when posting. This way Textile will not be broken by br or p tags created by PFF.
I would always recommend to post as draft and do the fine tuning in the TXP article editor. It is definitely NOT recommended to post immediately if you use Textile! Textile paragraphs are broken by the double-br effect. If you only use HTML in the whole article and you don't use excerpts it should be OK to post immediately to the appropriate section because Textpattern does not touch the HTML code as far as I know.
The fine tuning should be done in Textpattern after posting as draft which works fine with PFF. The fine tuning may contain custom fields, keywords, article picture, user defined URL, creation of an excerpt and the definition of the categories.
PFF issue: draft and del.icio.us
p.com issue: I wanted to post it as PFF issue but the project is gone!
There is a little if/else issue with PFF when posting as draft. If I post an article as draft and the del.icio.us publishing option is activated then a bookmark is created. Even worse if I edit the draft in PFF and the del.icio.us publishing option is activated and I keep the article as draft multiple d.i.u entries are created.
Shouldn't d.i.u bookmarking be automatically disabled when posting as draft?
I did not check the ping option but I believe it behaves similar.
Post new comment