Unable to approve #11116576

I've been unable to approve "[OT] Am I just a bad programmer?" [#11116576] — I tried a few times. The same problem was noted by davies: see the update to his "Re: [OT] Am I just a bad programmer?" response.

Looking at the moderation and janitation histories, two things happened at the same time ("2020-05-08 21:42" in my timezone):

The post was moved from SOPW to Meditations.
The post was approved (apparently in SOPW section).

We've previously seen this situation where a move and a subsequent approval were registered in the database out of order. I suspect this node is approved in SOPW so further attempts to approve it are ignored; however, as it's actually in Meditations, it's showing as unapproved in that section.

In the past, this has needed senior moderator intervention to fix. I've no idea of the exact cabal/level/other requirements.

— Ken

Comment on Unable to approve #11116576

Replies are listed 'Best First'.
Re: Unable to approve #11116576 by Corion (Patriarch) on May 09, 2020 at 06:05 UTC
Thank you for reporting this! The node had been approved while it was a SoPW, and moved to Meditations after that. Once a node has been approved into one section, it can't be approved into any other section. Removing the wrong approval made the node re-approvable.	[reply]
Re^2: Unable to approve #11116576 by davies (Prior) on Aug 28, 2020 at 20:42 UTC
I've just had the same issue with When Perl saved the day (and Python couldn't). Remembering this thread and my previous woes (link in the OP), I made sure I had moved it before approving it. The moderation history implies otherwise. Could there be some sort of race condition whereby the database had not been updated with the move by the time I approved? If this is not fixable (I understand the age of the code base), is there some way of warning moderators not to approve for $time after moving? Regards, John Davies	[reply]
Re^3: Unable to approve #11116576 by erzuuli (Cannon) on Aug 30, 2020 at 18:05 UTC
I'm not sure, but I think it's not a matter of time but rather that something gets cached in your browser, or rather, in the CGI parameters. Try reloading the node afresh a couple times before approving. Make double sure that the node has been converted to the new type.	[reply]
Re^4: Unable to approve #11116576 by davies (Prior) on Aug 30, 2020 at 21:26 UTC


XP is just a number
	PerlMonks