in reply to Re^3: Unable to front-page a node
in thread Unable to front-page a node

Thanks for the speedy reply.

"I wouldn't say the root cause is found."

That's a fair enough comment. I've <del>eted the word "root" from that sentence.

I seem to recall that, long ago, I did try that "node history" link on quite a few posts. It always told me:

"This node has not been edited yet."

I just tried it again, on one of my nodes that I knew I had edited, and got the same result. It doesn't look like it'll be much good when "considering empty nodes" (as I suggested earlier).

— Ken

Replies are listed 'Best First'.
Re^5: Unable to front-page a node
by jdporter (Paladin) on Feb 06, 2017 at 21:46 UTC

    The edit history includes content edits made to a node by someone exercising janitorial powers, but not by the node's owner.

    It also, currently, shows section changes. It does not show approval changes. (This could, and arguably should, change.)

    The Approval Nodelet can be used to see the current approval status, which is normally all you should need. Just remember to unapprove from a section -- and reload the node a couple times just to make sure, as some caching happens at some level in the stack -- before approving it into a different section.

    I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.
[reply]

      Thanks for the additional information. That certainly clarifies the meaning of the "This node has not been edited yet." message.

      I have moved a number of unapproved nodes without any problems. I don't have the necessary authority to unapprove a node: if an approved node needing moving, I'd consider it (Edit: move to ...).

      — Ken

[reply]
Re^5: Unable to front-page a node
by LanX (Saint) on Feb 06, 2017 at 22:26 UTC
    Yes the name is misleading.

    I was also surprised to finally find its purpose.

    Cheers Rolf
    (addicted to the Perl Programming Language and ☆☆☆☆ :)
    Je suis Charlie!

[reply]

      We should probably change that to read This node has not been janited yet. Concurrences?

[reply]
        I meant the title "edit history", it makes me think of a version control view of author actions.

        Maybe something like "admin/janitor/approval history" would cause less confusion?

        YMMV ...

        Cheers Rolf
        (addicted to the Perl Programming Language and ☆☆☆☆ :)
        Je suis Charlie!

[reply]

In Section Perl Monks Discussion