Saturday 11 December 2010 9:34:58 am

There seems to be a small typo on Step 8:

I guess "not" should have been "now".

Nice tutorial, posting Twitter updates is a perfect use case for workflows!

However, the used process of authorizing eZ Publish to have access to the twitter account looks quite cumbersome to me. I guess it could be made a lot easier by offering a screen for that in the eZ Publish administration interface that starts the full web-based authorization process instead of the out-of-band/PIN code authentication which was not really suitable for this kind of app. A good example of how this is done is the nxc_twitter extension available at http://projects.ez.no/nxc_twitter.

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Monday 13 December 2010 4:46:56 am

Hi,

Excellent article which shows the power of workflows and how thing can be easily done with it.

However, I just regret you don't put some examples on how debug thoses workflows, it can be tricky for some people.

Max

maxime.thomas@wascou.org | www.wascou.org | http://twitter.com/wascou

Maxime Thomas
maxime.thomas@wascou.org | www.wascou.org | http://twitter.com/wascou

Company Blog : http://www.wascou.org/eng/Company/Blog
Technical Blog : http://share.ez.no/blogs/maxime-thomas

Wednesday 15 December 2010 4:50:29 am

Thank you all for the feedbacks. Very much appreciate it.

@Kristof, I've notified Nicolas to see if the typo can be corrected. Regarding the Twitter API you are correct, this is not the easiest way to handle this and NXC technique is sweet. But this allows one to also discover eZ Script.

@maxime, I usually debug my workflows with eZLog::write() which is used here.