I've made several attempts to front-page "Turning very larger numbers into an array of bits" ([id://1181114]) without success. Each time, I've checked "FrontPage" and clicked "moderate"; some processing appears to occur; then the page is displayed with "FrontPage" unchecked: no errors or warnings are emitted.

The page is currently approved. It appears correctly (as far as I can tell) in: SoPW; RAT; and Newest Nodes. I can access the page from all of those places. It does not appear on the Front Page (i.e. it's not just some issue with the "FrontPage" checkbox display).

Other than that, it appears to be functioning normally: I have no problems viewing it; I've voted on it; I've voted on a reply; I've replied to it myself.

— Ken

Replies are listed 'Best First'.
Re: Unable to front-page a node
by Corion (Patriarch) on Feb 05, 2017 at 15:04 UTC

    Your initial frontpaging had even been recorded in the database, but for some reason it did not stick or frontpage that node.

    That row prevented further frontpaging attempts from taking place.

    I've deleted all the approval nodes from the database and was able to then approve and frontpage that node.

      ++ Thanks for investigating; reporting the problem; and resolving the issue.

      — Ken

Re: Unable to front-page a node
by LanX (Saint) on Feb 05, 2017 at 12:11 UTC
    Just a guess:

    edit history says it was moved to mediations and back.

    I think this somehow broke the mechanism, we had similar issues with such dependencies in the past.

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

      No, it was broken before that. This was to test if front paging would work if the node was re-sectioned (it still didn't work).

      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

        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!

      I wonder why such an experienced monk would move such an obvious SoPW to Meditations, and then back again; all within the same minute.

      For the side effects perhaps?


      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority". The enemy of (IT) success is complexity.
      In the absence of evidence, opinion is indistinguishable from prejudice.