I finally got the AdminRequestSanitizer to spit out some debug (shouldn't it have been as simple as calling the setDebug function with an argument of true?). It looks like part of the issue is that EO uses the variable named "id" (just like the storefront) to hold those added-products' attributes and the built-in 'id' definition is taking precedence:
Note: I don't think it's a possibility to change that 'id' variable's name; there might be other non-EO code that's making use of that variable and I don't want to create a real train-wreck.Code:May-13-2016 11:51:00 ================================= Incoming GET Request Array ( [page] => 1 [oID] => 8421 [action] => add_prdct ) Incoming POST Request Array ( [securityToken] => cb8ec48cbfe04dbde8aeb3dd0a4f7b34 [id] => Array ( [35] => Array ( [value] => 2271 [type] => 0 ) [48] => Array ( [value] => 3244 [type] => 0 ) [43] => Array ( [value] => 2406 [type] => 0 ) [20] => Array ( [value] => 2259 [type] => 0 ) [44] => Array ( [value] => [type] => 1 ) ) [add_product_categories_id] => 110 [add_product_products_id] => 287 [search] => [step] => 4 ) Running Admin Sanitizers PROCESSING SIMPLE_ALPHANUM_PLUS(GET) == action PROCESSING SIMPLE_ALPHANUM_PLUS(POST) == id PROCESSING SIMPLE_ALPHANUM_PLUS(GET) == oID PROCESSING SIMPLE_ALPHANUM_PLUS(GET) == page PROCESSING STRICT_SANITIZE_VALUES == securityToken PROCESSING STRICT_SANITIZE_VALUES == add_product_categories_id PROCESSING STRICT_SANITIZE_VALUES == add_product_products_id PROCESSING STRICT_SANITIZE_VALUES == search PROCESSING STRICT_SANITIZE_VALUES == step Outgoing GET Request Array ( [page] => 1 [oID] => 8421 [action] => add_prdct ) Outgoing POST Request Array ( [securityToken] => cb8ec48cbfe04dbde8aeb3dd0a4f7b34 [id] => Array ( [35] => Array [48] => Array [43] => Array [20] => Array [44] => Array ) [add_product_categories_id] => 110 [add_product_products_id] => 287 [search] => [step] => 4 )


Reply With Quote
