it cost me 21h of debugging my system to death … thank you, eggheads!
I am the fiercest enemy of “it just happens, I did not do anything” … the most stupid lie ever, but in a way I had to chew on it
suddenly, after pressing a button on a wp plugin admin page a 500 error popped up and shortly I was misguided by the nature of 500, which normally by definition is a server error …
monkey feature part one is, that the shameless wp-dev who dragged it in, camuflaged it as if it was a 500, but it was just a miserable trick hiding what it really was …
I will not tell the whole story, so the short version is, it was in the names
this it was:
<select name=”post_type” id=”post_type”>
silently, immediately on button press, wp threw the 500 out, while this:
<select name=”p_type” id=”p_type”>
went through normally as before …
IT IS JUST A NAME, what’s the brain vacuum level of whom who did that?
here the prove of it being not only vacuum, but also quite close to zero kelvin in that genius’s brain:
this works now:
$p_type = sanitize_text_field($_POST[‘p_type’] ?? ‘post’);
but this too:
$post_type = sanitize_text_field($_POST[‘p_type’] ?? ‘post’);
defintely nuts, but it’s still missing the key for “it suddenly happened”, where is it ?
here it is, last week I upgraded to wp 6.83 … somebody put a box of rats into that upgrade just in order to sabotage honest people’s work
now it is a full monkey feature sticked on my wp’s wall of shame
then I thought, maybe those wp guys are losing it and it was just a way to say: who’s the boss? we are …
and I thought, but not anymore …
wp’s latest monkey feature
hakka quote … we don't throw code away – we absorb its lessons and evolve beyond its limitations

Leave a Reply