Originally Posted by
chibipaw
Whoa..... That actually worked.
I thought everything in that field is purely cosmetic, and wouldn't have anything to do with the parsing.
Now Im thinking to myself, is this a feature or a bug? Hard to tell.
Thank you very much!
really? shocked that we resolved this? please....
as to feature or bug, i would go with bug. my educated guess (actually i'm pretty sure) is that the sanitizer cleansed the $_POST['audience_selected'] variable so that there was no match against the query_builder table. potential solutions would include not cleansing that variable, or to use the query_id as opposed to the query_name as the option value for the audience_selected. you can see the code here using my query_builder table:
Code:
<select rel="dropdown" name="audience_selected">
<option value="" selected="selected">Please Select</option>
<option value="All Newsletter Subscribers">All Newsletter Subscribers (2871)</option>
<option value="Dormant Customers (>3months) (Subscribers)">Dormant Customers (>3months) (Subscribers) (2520)</option>
<option value="Active customers in past 3 months (Subscribers)">Active customers in past 3 months (Subscribers) (0)</option>
<option value="Active customers in past 3 months (Regardless of subscription status)">Active customers in past 3 months (Regardless of subscription status) (0)</option>
<option value="Administrator">Administrator (1)</option>
<option value="Customers who have never completed a purchase">Customers who have never completed a purchase (478)</option>
<option value="Permanent Account Holders Only">Permanent Account Holders Only (4015)</option>
</select>
if the option value used the query_id, we would not have this problem. else you want to be very careful about what you use as your query_name.
glad that we resolved it.
best.
Bookmarks