KDE - Blog from KOrganizer HOWTO

Blog from KOrganizer? What kind of madness is this? Apparently some crazy fool decided to give you the ability to post journals from KOrganizer to your blog. Let’s learn how to do it!

Firstly open KOrganizer.

When it has opened right-click anywhere in the “Calendars” area in the bottom-left and select “Add…” from the drop-down menu that appears.

Select “Journal in a blog” from the “Resource Configuration” dialog.

Fill in the “Resource Configuration” dialog.

  • Name: Choose a descriptive name for your resource, this is how KOrganizer will describe it to you in future. KOrganizer won’t reference this resource as being a blog again so you may want to choose something suffixed with “blog”.

  • XML-RPC URL: This depends on your blog but for Wordpress and Drupal this is the main URL followed by “/xmlrpc.php”, for LiveJournal it is “http://www.livejournal.com/interface/blogger” and for Blogger it is “http://www.blogger.com/feeds/$YOUR_USER_ID/blogs”. For other blogs, consult their documentation or ask me for help and I’ll do my best to work it out.

  • Username: This is the username you use to login and make blog posts.

  • Password: This is the password you use to login with the above username and make blog posts.

  • API: Use “(Wordpress, Drupal < 5.6 workarounds)” if you use either of those blogs. Otherwise it is MovableType for Drupal, Google Blogger Data for Blogger and Blogger for LiveJournal. The LiveJournal API is unlikely to work with LiveJournal as it isn’t yet complete. If you wish to implement the LiveJournal full API rather than using legacy Blogger one then please contact me.

  • Blog: When you have chosen an API this list will be automatically populated using items from the server. If there is only one entry, it will be greyed out but the entry’s text shown and selected. If there are more than one (e.g. Drupal has one for pages and one for posts) they will be selectable. If there is nothing new displayed then one or more of your XML-RPC/username/password/API are probably incorrect.

  • Posts to download: This chooses how many posts the API will download and sync. If you, like me, have made hundreds of posts then you probably want to keep this number reasonably low.

  • Automatic Reload: This defines how often KOrganizer will download new blog posts from the server without notification.

  • Automatic Save: This defines when KOrganizer will upload new blog posts to the server without notification. You probably don’t want to have this set to “On every change” unless you want it to be uploaded as soon as you hit “Save” in the next view.

You should now see your new blog resource displayed in the bottom-left corner. Let’s try making a new blog post. Activate the journal view by clicking the journal button.

We are now in the journal view and you can see on the left-hand pane that KOrganizer has successfully downloaded some of my blog posts. If we want to create a new one then click on the add journal button.

Fill in the “Edit Journal Entry” dialog.

  • Title: You probably want to change the title of the blog post from the default.

  • Date/Time: On most blogs selecting the date/time to somewhere in the future means the blog won’t publicly appear until then.

  • Content: Write something about how I am awesome, like the pictured example.The rich-text should be displayed on your blog correctly (albeit with slightly nasty HTML).

  • Select Categories: This list should have been populated with the ones from your blog and from the KOrganizer defaults. Sadly, I can’t seem to remove the latter and selecting them will do nothing unless they have been created on your blog.

When you click “OK” you may be prompted which resource you wish to save to. Select the resource we just created.

If you chose “on every change” for “Automatic Save” in the “Resource Configuration” dialog then your post has probably whizzed its way off to your blog already. If not, you can manually save it by right-clicking on your resource and selecting “Save” from the drop-down menu that appears.

I hope this was and is useful to some people. If you find any bugs, have any problems or want any other features then please let me know either by email, my posting on this blog or by filing a bug in the KDE bugtracker.