I've been using this module on my site for a few months now and during this time I haven't used Revisions.
Few days ago I enabled Revisions for a Content Type. Since then all Nodes with stored Revisions are shown first in Relevant Content blocks.

Comments

nicholasthompson’s picture

nicholasthompson
Primary language English
commented

Interesting - I'll have to find time to take a look at that. Stupidly busy at the moment.

realOFF’s picture

realOFF commented

I'll try to illustrate the problem:

Node A - No revision
Term 1, Term 2, Term 3

Node B - Recent Revision
Term 1

Node C - No Revision
Term 2, Term 3

Given the above Nodes with their respective associated terms, I have recently created a revision for Node B...
Normal behaviour for this module would give list in this order:
Relevant Content for Node A
- Node C
- Node B

But, as I have a revision for Node B, list results in:
Relevant Content for Node A
- Node B
- Node C

Even if there are other Nodes with more relevance to Node A, Node B will be listed first as long as it has one Term in common.

I hope I have made myself clear enough to help you understand the problem.
Really useful module. Thanks!