noemail and cc params - Do they work?

@TobyL,

Shouldn’t &cc work at the same time as &to ? ... I have been defining emails in &cc, but not receiving them. I am, however, receiving emails if I comma delimit in the &to param ...Just nothing via cc seems to get sent?

If I passed

&noemail=`false`

, would it still mail? Technically, if I define the param, but setting the boolean value to false I would expect that it would. Have you done any testing with this type of a setup?

`1` and `0` seem to work better than `true` and `false` in snippet parameters for some reason.

Quote from: sottwell at Nov 17, 2006, 05:42 AM

`1` and `0` seem to work better than `true` and `false` in snippet parameters for some reason.

Per OpenGeek, all snippet parameters are treated as strings, and the string ’false’ will evaluate logically to a boolean true.

//<?php
    noemail => isset($noemail)? true:false,

//<?php
    noemail => isset($noemail)? 1:0,

//<?php
    noemail => isset($noemail)? $noemail:0,

//<?php
if( !$noemail ) {

//<?php
if($noemail!=false) {

I am still experiencing mail being sent when not desired, passing 1 or 0...I believe this code is overriding it:
Code:

//<?php
    noemail => isset($noemail)? true:false,

OR Maybe this would be better:

Code:

//<?php
    noemail => isset($noemail)? $noemail:0,

//<?php
    noemail => isset($noemail)? $!(!$noemail):false,

Update: Hmm...I tried both, and was receiving similar results....It turns out, I had to modify the core in order to get emails to drop: