Hi,

I have set the pub/sub scenario between the two instances
and set the channel `When should content be published?` to `As soon as it is submitted/updated`.

Problem happens when node on publisher is updated, it sends the `node_load` cached version of the node content.
example:
1. node is created on publisher (e.g. title:test1 body:test1.1)
2. node is automatically pushed on subscriber (great stuff!!, everything works: creates a node, terms, cck's)
3. same node is updated (e.g. body: test 1.2)
4. node is pushed, and node on the subscriber is updated, BUT it has the same content (e.g. body: test 1.1)

Problem is in the (line:306) `publish_publish` function

line 307: $node = node_load($nid);
it should be a
$node = node_load($nid,NULL, TRUE);

so that way node_load cache gets cleared and it loads the new updated version of the node.

Comments

voidberg’s picture

Assigned: Unassigned » voidberg
esteewhy’s picture

Faced the same (mis)behaviour - node updates appear on client late by 1 revision.