Thanks for the reply, doodlebee.
“I can add new ones, but I can’t edit them” – but what I didn’t say was “The old ones behave the same way.” So… it’s ALL posts…
In trying to troubleshoot this for myself, I was (as I mentioned) looking into adding some debug code.
Using brute force and ignorance, I added code designed to stop it in its tracks, specifically
die("message of some sort");
Progressing through the post.php code, in the ‘edit’ section, I found that it was getting to the right place, evidently finding the right post, and then… for you code monkeys, this should be a clue, right here… starting around line 76 is the following:
if ($post->post_status == 'static')
include('edit-page-form.php');
else
include('edit-form-advanced.php');
Not wanting to interrupt this, I copied it and changed the “include” to “die” so it would tell me which one was selected:
if ($post->post_status == 'static')
die('edit-page-form.php');
else
die('edit-form-advanced.php');
I put this code AFTER the “include” code, and my expectation was that it would hit one of those two, show the message and stop right there.
But NOOOOOOOO! Instead it blew right past ’em and brought up the EDIT screen!
I’m investigating. I don’t quite understand why it should do that (not knowing any more about PHP than I do at this point) but I have a feeling that the “include” actually pulled in the referenced code and started running it – although I would have expected it to do that anyway – and there’s something about having code AFTER the “include” that gives it something to work with…
If you have any insights, I’d be happy to hear ’em.
–LATER
Sho’ nuff, I put the “die” code ahead of the “include”, and it does die.
What I’m thinking is that the “include” code goes ahead and includes the code from the referenced file right at that point and begins executing it right then… and apparently never returns to that point (which is why it doesn’t “die” afterward)… seems a bit strange, but maybe dat’s de facks?
