This is a minor, minor issue... Coming from someone who's relatively new to this module, I thought these small changes for the settings page might make things a little more immediately clear.

Specifically, these changes to text strings in revisioning_admin_configure():
- Change "displaying the current revision" to "displaying the published revision"
- Change "edit the current revision" to "edit the published revision"
- Change "...reverts to current revision, if the user..." to "...reverts to published revision, if the user..."

I'm thinking that it's more obvious what the difference is between 'published revision' and 'current revision' instead of 'latest revision' vs 'current revision'.

Just a thought!

Comments

rdeboer’s picture

rdeboer
Location Melbourne
commented

Your feedabck is much appreciated Kendall!
I think some refinement in the wording is a good idea.
I have one reservation though... technically every node has a "current revision". Even when the node is not yet published or previously published, it still points to a current revision... of all the revisions associated with a previously/not yet published node that's the one that will be the 'published revision' when you click "Publish current".
Maybe I should change the code to use 'published revision' (when the node is published) and 'pubication candidate' when it is not.However the latter suggests that revisions other than the candidate cannot be published, which is not true.
Language... you got to love it...

rdeboer’s picture

rdeboer
Location Melbourne
commented
Status: Active » Closed (fixed)

No activity for 3 months. Closed.