Subscribe2 and WindowsLive Writer

What version of Subscribe2 are you using?

Did this work in previous versions of WordPress do you know (before 3.2)?

WordPress 3.3 and Subscribe 7.0.1
I can’t be positive but I think it did work with earlier versions.

I am also noticing this issue, worked pre-3.2, Have updated to latest version of WordPress and Subscribe2

I can still send messages manually through Subscribe2 but no auto notifcation is sent out when posting via LiveWriter

Thanks guys,

I’m doing some digging. I don’t personally use Live Writer so can you describe the process for me?

It uses a feature in WordPress called XML RPC. At the moment I think it’s possibly down to one of 2 things:

1/ Plugins are not being loaded in WordPress 3.3 when posts are made through XML RPC.
2/ The post transition hooks are being fired differently somehow.

No, with respect to the latter of these there may be a little fix. I think new posts made through XML RPC may get an initial post_status of ‘auto-draft’ and if these are then moved to a published state without being saved first then Subscribe2 won’t get fired.

Try looking in the subscribe2.php file, towards the very end there is a function called subscribe2() and it contains the following:

add_action('new_to_publish', array(&$this, 'publish'));
add_action('draft_to_publish', array(&$this, 'publish'));
add_action('pending_to_publish', array(&$this, 'publish'));
add_action('private_to_publish', array(&$this, 'publish'));
add_action('future_to_publish', array(&$this, 'publish'));

Try adding this to that same section:
add_action('auto-draft_to_publish', array(&$this, 'publish'));

MattyRob:

The line addition to the file worked for me. Thanks.

Windows Live Writer is hugely popular — it works well, and you might try it yourself — so you might expect this problem to be widespread. The new line should be part of the next upgrade.

@bellarush,

Thank you so much for confirming the fix – it’s so difficult when you are trying to figure out what could be going wrong from just reading the code!

I’ll certainly get this fixed rolled into the next version.