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

So, the editing wasn't the issue: Corion has identified the root cause; and, as Arunbear indicates, the editing occurred later.

I was aware that moving pages between sections had, in the past, caused problems with both approval and front-paging operations — given the node was by a first-time poster, using the wrong section was certainly a possibility — however, I didn't know how to check this. There was no indication in the thread that anyone had done this; I also checked "Nodes to Consider" to see if a "move to section ..." was perhaps in progress (it wasn't).

Anyway, thanks to your "edit history" link, I find I can just add ";displaytype=edithistory" to the query string to get this information. This will be useful, not just in similar situations to this one, but also when considering empty nodes: Edit (to restore content) or Reap (it's genuinely empty). With that in mind, is this functionality available from, say, some Nodelet, or do I need to manually edit the URL?

— Ken

Replies are listed 'Best First'.
Re^3: Unable to front-page a node
by LanX (Saint) on Feb 06, 2017 at 20:53 UTC
    I wouldn't say the root cause is found.

    Regarding "node history" check the "approval nodelet".

    But better don't be too optimistic, imho it doesn't show much more than changes triggered from the approval nodelet.

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

[reply]

      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

[reply]
[d/l]

        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]
        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]

In Section Perl Monks Discussion