This plugin enables the blog owner to publish their posts on a xmpp pubsub
node. This way, anyone subscribed to this same node will be notified through
Jabber when a new post is published.
It enables also to do the same with comments on separated xmpp pubsub nodes, so
that readers can also subscribe and get notified about new comments of a
specific post only if prefered.
Note: this is a early version, you can try it if you are interested (there can
be no harm! ;-), but I will provide far better versions progressively…
- Connection with SRV records, TLS if available and known authentication
mechanisms (in this order of preference): Digest-MD5, CramMD5, PLAIN,
- Posts are published on the subnode posts/ of the given pubsub node;
- Comments are published on the subnode comments/ with being the id
of the corresponding post;
- Posts, as well as comments, are deleted automatically from the associated
pubsub nodes if you delete them, disapprove them, or flag them as spam from the WordPress website;
- Posts, as well as comments, are updated automatically on the associated
pubsub nodes if you edit them on your WordPress website;
- Autodiscover xmpp link for all posts is automatically set on all pages,
except single posts (if the ‘wp_head’ function is used by your theme, which is
the common procedure);
- Autodiscover xmpp link for comments of the current post is automatically set
on each single post (if the ‘wp_head’ function is used by your theme, which is
the common procedure);
- 2 templates functions for returning or displaying different xmpp links are
provided for your themes.
In the ‘Jabber Feed configuration’ menu, you will see the following sections:
This section contains the connection parameters of the account which will be
used to publish the field. I would personnaly advice to create a new account
just for it (you can also use your personal account of course, anyway the plugin’s
bot will create a resource identifier unique for every connection) and to
configure it to refuse any contact and communication (as noone will have to
add it to one’s roster, except you maybe for test or debugging purpose?).
The fields are:
- The bot adress (full jid form: mybotname@myserveraddress);
- the password.
By default Jabber Feed can now use SRV records which is a recommended way to
advertize server and port from a domain name (see for instance
http://dns.vanrein.org/srv/ for details).
This is an advanced section in case your server does not use SRV AND uses a server
which is not the same as the domain from the jid or a port different from the default one (5222).
Hence there will be very very new cases where you will have to fill this
section and if you don’t understand all what I say here, just don’t fill
anything here (if you fill even only one field, then it will be used instead
of SRV and default values).
The default values will be used if fields empty and no SRV is configured on
the Jabber server:
- the Jabber server (often the same as ‘myseveraddress’ of the jid);
- the Jabber port (usually 5222).
Where to publish the notifications. It can be on a separate server.
- the pubsub server;
- the root publication node;
- 2 checkboxes to uncheck if you don’t want to publish the posts or the comments.
Note that this node does not have to exist. When you will press the “Update”
button, the providden Jabber login and connection parameters will be tested
and the node will be created with all its tree. If anything goes wrong, you
will be informed about it.
The providden Jabber account can have no right to create the required post/
node, but then it must be created first and publisher rights at least must
have been given.
The page with the list of published posts have been modified. A new column
called “Jabber Feed” will display:
* The publication date on the node (and the last update will appear on a
bubble when the mouse passes by);
* ‘Error on publication’ when an error has occured during publication (and the
error text will be displayed when the mouse passes by);
* ‘Not Published’ when no publication never occurred (which is simply when the post has
been published on WordPress before the plugin has been installed.
TTL support for DNS/SRV records.
Still need to test extensively (and if necessary improve) the right system
- will the non-approved comments be published on the comment nodes?
- will the private posts be published?
In the “configuration” window, I should make a detection of the
prerequisites, gray everything if a mandatory one is not fulfilled and give an
And what about internationalization?!
Manage menu: with failed publication, it should be possible to retry the
publication from this page (with multiple checkbox if possible to massively
And what about an equivalent of post management for comments?! Is it
possible (apparently not, according to WordPress documentation)?
The item should also be updated when a published post is edited.
Why not add support to pages? -> current work.
Create the bot account as well?
Why not retry to publish after a timer (let’s say 1 day?) after a failure,
with a number maximum of tries?
What could be fun: if the subscribers could be also publisher, hence
answering to a post by directly publishing to the node?
But how is a publisher identified?! No “from” with a pseudo in it, and data
about real jid accessible from admin.
Improve globally the
message syntax (for instance the message ‘updated’ and ‘created’ tags).
Configure the node instead of simply create it with default configuration.
Check the node authorizations if it is already existing.
Improve the internationalization strings (and set at least 2 default
languages: English and French).
And what if the post or page is private? Should it be added on a node? Maybe
a node with a white list that the admin can manage?
Apparently if I disapprove or flag a comment as spam from the “edit comment”
page, it does not remove it from the node. Why? Is it a bug from WordPress
which does not trigger the action in all cases? Or is there another WordPress’
action for this specific case? Try this also with posts from the “edit post”
Edit: it seems to be a known bug: https://trac.wordpress.org/ticket/5792
Is planned to be fixed for WordPress 2.9 apparently.
=> this seems to be fixed now! Woohoo!
Add more authentication mechanisms? (current: Digest-MD5, CramMD5, PLAIN,
ANONYMOUS. Only Digest-MD5 and PLAIN has been tested)
SSLv23 added, but what about TLS? (TLS does not work on Gmail. SSL and TLS works on ejabberd. So
I have decided to use SSL only for now)
Note that it looks like the PHP implementation of TLS encryption does not seem
like verifying the certificate…
Add poster/commenter name in ATOM format.
Add support for button of publishing all posts in once…
Propose max_items to change…
Improve title naming (different for comments, posts, and even for comments
of each posts…)
Isn’t there a configuration option for getting notif of subnodes?.. Seem to
You can have some news about this plugin on my freedom
haven or of course, by
subscribing on the following xmpp pubsub node:
If you want to contact me by jabber, ask me first by email (which you can find
on my website. Yes I know, this is complicated: but I like my tranquility, so
I make a filter).
Have a nice life!
- Upload the plugin archive to wp-content/plugins/ directory on your WordPress installation;
- Uncompress it by keeping it in its own sub-directory called jabber_feed/;
- Activate the plugin through the ‘Plugins’ menu in WordPress;
- Configure the plugin through the appearing sub-menu ‘Jabber Feed configuration’ under the ‘Plugins’ menu.
- When aknowledging the configuration by pressing the “Update” button, the
jabber login will be tested and the pubsub nodes created. Hence if anything is
wrong with your configuration, you will be immediately informed.
- This plugin also defines two templates:
jabber_feed_get ($node = 'posts', $what = 'url', $text = '') will return a string being a url (bare, or in a ‘a’ or ‘link’ tag).
jabber_feed_display ($node = 'posts', $what = 'url', $text = '') is the same as the previous template but display the string instead of returning it!
These template functions can be used in your theme.
Note that if your theme uses the ‘wp_head’ function in its header (most cases), a autodiscovery link on the post node will be automatically generated in the header. Otherwise, you can add it by yourself with these functions for instance.
PHP must be built with the option
--enable-socketson PHP 4 >= 4.0.7 or PHP 5 (though I haven’t tried with such a version, with PHP 5.3.0 and more, this extension is moved to the PECL repository!). If you have an error relating to socket, this is most likely a dependency issue.
Note for gentoo users: you must set the ‘sockets’ USE flag.
It uses the library ‘expat’ to parse XML (enabled with the
option of the php compilation).
Note for gentoo users: you must set the ‘xml’ USE flag.
It uses the
Auth_SASL PEARmodule (
pear install Auth_SASLor install with your distribution’s package manager) for SASL authentication. For now, this dependency is mandatory because this is the only supported authentication mechanism. Maybe in some future will it become optional.
OPTIONAL: to have the option of sending formated notification in XHTML, the “tidy” PECL extension must be installed.
It is based on the libtidy library which must first be installed: http://tidy.sourceforge.net/
Then with PHP 4.3.X or PHP 5, you can install it as a PECL module:
pecl install tidy; or with the
–with-tidy compilation option in PHP 5.
Without this, you won’t have access to the XHTML option and all notifications will be sent as a normal textual message.
OPTIONAL: if the plugin is installed on a BSD (Mac included),
in order to use the SRV records on the admin JID, which is the correct way of resolving the server and port addresses for a domain, the PEAR extension NET_DNS must be installed: ‘pear install NET_DNS’ (Note that it will ask to have php compiled with ‘mhash’ option).
If it is installed on Windows, it is not anymore mandatory if you have PHP
5.3.0 or later installed (under this version of PHP, you should also install
this extension to benefit SRV records).
Linux servers do not need this extension to have SRV.
Note for gentoo users: you must set the ‘mhash’ USE flag.
This script has been tested only currently on WordPress 2.0 up to WordPress
2.9.1 with PHP 5.2.1 to 5.2.11, running on a GNU/Linux 64 bits (Gentoo Linux).
Hopefully it should work with other software versions (not for PHP4, because
of the TLS feature with is PHP5 specific. Yet if you are really interested
into PHP4 compatibility and if TLS is not required for your connection, just
ask me, I will try to make a compatibility layer), but I cannot guarantee.
Tell me please if you tried this successfully with another configuration so that I update the known working platforms list.
At the opposite, if you find a bug or encounter an issue on some configuration, don’t hesitate to tell me, and I will try and fix it.
Examples for using the function templates
jabber_feed_get and `jabber_feed_display` have the same parameters, but the
first returns the link whereas the latter displays it:
jabber_feed_get ($node = 'posts', $what = 'url', $text = '')
jabber_feed_display ($node = 'posts', $what = 'url', $text = '')
- ‘node’ can be ‘all’, ‘posts’, ‘pages’, ‘comments’, ‘current’ (comments of
the current page/post) or a number (comments of the given numbered post/page);
- ‘what’ can be the bare ‘url’, or included in a ‘a’ tag, or a ‘link’ tag;
- ‘text’ is optional displayed text (only when ‘a’ tag).
So for instance, if the pubsub server is ‘pubsub.jabber.org’ and the node is
jabber_feed_display ('posts', 'bare')displays simply:
which is a bare url of the node containing all the posts.
jabber_feed_get ('comments', 'a', 'All the comments')will return:
<a rel='alternate' href='xmpp:pubsub.jabber.org?action=subscribe;node=blog/comments;subscription_type=items;subscription_depth=1'>All the comments</a>
which is a link for all comments.
jabber_feed_display (5, 'link')will display:
<link rel='alternate' href='xmpp:pubsub.jabber.org?action=subscribe;node=blog/comments/5' />
which is an autodiscovery link for the comments of post 5.
- Question from myself: how people can subscribe on a Jabber node?
Unfortunately this plugin is rather a “proof of concept” plugin as long as
there is no Jabber client allowing users to easily subscribe (and configure
their subscription) to xmpp pubsub nodes.
I could use Gajim to subscribe to nodes though, but I had much difficulty to
“browse” nodes with it, and it is impossible to create a node (at least I have
As for Psi, I could not do any subscription at all.
The only mean for the time being is to use a client with a XML console (the
only ones I know with such a console are Gajim, Psi, and Sameplace with an
official plugin) and send this raw XML subscription (which is indeed a non very
user-friendly method, I must admit).
It would be nice if people could implement soon a node subscription feature in
their favorite Jabber client (I will probably try to do so myself as a next
step) and also a relation in their favorite web-browser to Jabber links (so
that they could have their Jabber client propose them to subscribe and
configure a node just by clicking on a link on their browser).
Hopefully then I will update this readme to advice such Jabber client and web
- From myself: which jabber server has a good pubsub implementation?
I am using ejabberd 2.0 and 2.0.1 for my own, but it is pretty flawed on many ways.
Especially it is impossible to configure your subscription to a node. What a
Anyway it is sufficient basically for the proof of concept, but probably not
for long-term (even mid-term) real use.
Yet I heard that the coming development version of ejabberd (3.0) has had a
rewrite of the pubsub implementation. I have not tested though.
I don’t know sufficiently others server softwares to give an opinion about
them. But I was told Openfire should have soon a pretty good PubSub support. I
am still waiting to test it though.
- From myself: which Jabber client could I advice to visitors of my website?
As explained, there are few, if none, clients with good PubSub support. This
is why I told this plugin is more a proof of concept than an useful one. But
hopefully, soon it will be better!
Process One has developped recently a pubsub client called
far as I know, the first one ever publicly released, fully dedicated to
pubsub. I had only one review from someone, not so enthousiast though. For my
own, I have unfortunately been unable to test, as it uses Flash technology
(Adobe AIR) and my MIPS computer does not take Flash very well (usually it
will crash, if it works at all, anyway). If someone had a chance to test it
with publication generated by my plugin, I would be happy to get a feedback…
- From myself: but no browser can detect XMPP autodiscovery links. What are they for?!
I am writting a small Firefox plugin for this. Soon more infos!
- Do you like to ask questions to yourself? Do you feel lonely?
Contributors & Developers
“Jabber Feed” is open source software. The following people have contributed to this plugin.
Better SRV library gestion: the plugin can now “switch” between the NET_DNS library
if installed, to the core PHP SRV functions (if using Linux or a Windows
with a recent PHP) or nothing (no SRV gestion).
Hence for Linux or Windows (with recent PHP), no additional library is
Algorithm for dealing with priority and weight of target in SRV records is
now implemented, exactly as in RFC 2782. Therefore the only missing part for
a full SRV records compliance is now a support of Time To Live, which could
be interesting next implementation.
New widget for displaying the XMPP feeds in the sidebars.