[TYPO3-timtab] frontend posting possible?

[Peter A. Schott]

Great post, Oliver.  I guess I'd already done most of the other steps, but
will need to investigate the clearPageCacheOnUpdate and the trick for
remapping the RealURL entry now that I have RealURL working.  :-)

I guess there is some confusion on the MetaWeblog API - it worked fine for
ScribeFire (FireFox plugin), but w.Bloggar and Live Writer both had issues
with categories without descriptions.  Of course, Live Writer was able to
maintain the formatting while w.Bloggar and ScribeFire both lost all
formatting when posting.

Still, I had success using a 3rd party tool to post which made all the
difference to me as it will make a world of difference to our Staff members.
I've pretty much started to understand the TYPO3 interface, but it will
definitely confuse all of them.

-Pete Schott

Oliver Rowlands <oliver at liquidlight.co.uk> wrote:

> Hi Oleg,
> 
> I've managed to get timtab working with Windows Live Writer 
> (http://writer.live.com/) and the MetaWeblog API but it did require 
> modifying a few things in timtab's web services source code. The 
> MetaWeblog API spec is so vague that it has been interpreted in many 
> different ways by many different vendors. Of course timtab is not to 
> blame, the Microsoft developers simply did not implement the spec 
> correctly  ;)
> 
> You can find a comprehensive list of other MetaWeblog complient clients 
> on Wikipedia:
> 
> http://en.wikipedia.org/wiki/MetaWeblog
> 
> Anyway in order to get the Metaweblog API enabled you will have to do 
> the following:
> 
> - Enable the the 'Blog Webservices (timtab)' static include in your root 
> template: 'List' mode > Click the page title of the page containing your 
> root template > Edit the template > Select 'Blog Webservices (timtab)' 
> in the 'Include static (from extensions)' field' > Save and close.
> 
> - Add the following TS to your root templates TS constants:
> 
> plugin {
>    tx_timtab {
>      homepage = http://[DOMAIN]/path/to/blog/
>      title = [BLOG TITLE]
>      blogPid = [BLOG HOMEPAGE PAGE ID]
>      homePid = [SITE HOMEPAGE PAGE ID]
>      clearPageCacheOnUpdate = 1,31,169 # Insert a comma separated list 
> of page IDs which contain the tt_news / timtab plugins (LIST, SINGLE, etc)
>    }
>    tx_timtab_pi2 {
>      enableBlogger = 1
>      enableMetaWeblog = 1
>      pidStorePosts = [SYSFOLDER PAGE ID WHERE THE POSTS ARE STORED]
>      enableUploads = 1
>    }
> }
> 
> You should now be able to access your Metaweblog XML-RPC interface at 
> the following URI (this is the URI you should use in your desktop 
> publishing application) using your backoffice username and password:
> 
> http://www.domain.com/index.php?type=200
> 
> You can remap this page type in RealURL to a unique filename for example:
> 
> $TYPO3_CONF_VARS['EXTCONF']['realurl']['_DEFAULT'] = array(
> 
> [...]
> 
> 'fileName' => array(
>      'index' => array(
>        'rpc.xml' => array('keyValues' => array('type' => 200)),
>      ),
> 
> [...]
> 
> );
> 
> And you should then be able access it using the far more elegant:
> 
> http://www.domain.com/rpc.xml
> 
> I hope this helps,
> 
> Oliver
> 
> Oleg wrote:
> > Hi Peter,
> > I'll appreciate if can you give a more detailed example. What tool do 
> > you use?
> > 
> > Peter A. Schott wrote:
> >> It's possible to use blogging tools to connect.  I had that working 
> >> for my
> >> website.  You need to run through the various config options for RSS, 
> >> etc, but
> >> once you do that, you can:
> >>
> >> 1. point your tool at the blog page
> >> 2. Use a back-end login for username/password
> >> 3. Choose MetaWebLog API for the type of blog.
> >> 4. point to the blog page, but add "&type=200" for the posting URL.
> >>
> >> Once I did all of that, had no issues except with the categories.
> >>
> >> For some reason, categories are passed back with "categoryName" and
> >> "description" but MetaWebLog expects only description.  Easy to work 
> >> around -
> >> just be sure that your "Description" fields are filled out for all 
> >> tt_news
> >> category entries.