The first is rather large, but it’s not that, it was (and still is) working, as you’ll see. I did try changing the variable names, and just test for isset first
if (isset($_POST[’whatever’])) {
}
The second one is simple:
<?php
//[[!snippetname? &parent=`[[*id]]`]]
if (! isset($parent)) { return ’’; }
$content = null;
$table = $modx->getFullTableName(’site_content’);
$query = "select pagetitle,content from $table where published=1 and parent=$parent limit 1";
$res = $modx->db->query($query);
if ($row = $modx->db->getRow($res)) {
$title = $row[’pagetitle’];
$content = $row[’content’];
}
if ($content) {
$content = "
<div class=\"some-class\">
<h5>$title</h5>
$content
<div class=\"box-bottom\"></div>
</div>
";
}
return $content;
?>
It gets curiouser and curiouser. I’ve managed to duplicate it, just don’t know why or how it’s doing it.
I create a document, in that document’s template in one area is the placeholder for the snippet that accepts posts.
I create a second document that is a child of this document. In another part of the parent document is the snippet above (long story, think like (get a list of the titles for all children of this document.") So what happens is it’s reading this child and outputting some stuff.
As soon as I add the snippet for the second one to the template, poof, no post data and it 302’s. What’s REALLY weird - switching back to a different template, removing the snippet calls, whatever, nothing seems to make it work. It’s as if the sickness "sticks" to the database entry or something which is impossible.
CORRECTION: It’s not the adding of the snippet at all. I just re-did the above scenario again, everything was working fine. Posting fine but of course the snippet above doesn’t find any children.
As soon as I ad a child resource - poof. Goners. Remove the resource? Still broken.
BTW I’m clearing cache with every update too. Maddening. Boss’s face is red. :-(
