Do the same than parse_str without max_input_vars limitation

gistfile1.php

<?php

/**
 * do the same than parse_str without max_input_vars limitation
 * @param $string array string to parse
 * @return  array query parsed
 **/
function my_parse_str($string) {
  $result = array();
	// find the pairs "name=value"
	$pairs = explode('&', $string);
	$toEvaluate = ''; // we will do a big eval() at the end not pretty but simplier
	foreach($pairs as $pair) {
		list($name, $value) = explode('=', $pair, 2);
		$name = urldecode($name);
		if (strpos($name, '[') !== false) { // name is an array
			$name = preg_replace('|\[|', '][', $name, 1);
			$name = str_replace(array('\'', '[', ']'), array('\\\'', '[\'', '\']'), $name);
			$toEvaluate .= '$result[\''.$name.' = '.urldecode($value).'; '; // $result['na']['me'] = 'value';				
		}
		else {
			$name = str_replace('\'', '\\\'', $name);
			$toEvaluate .= '$result[\''.$name.'\'] = '.urldecode($value).'; '; // $result['name'] = 'value';
		}
	}
	eval($toEvaluate);
	return $result;
}

$array = my_parse_str($query);
?>

This has issues with strings - see my fork for a fix

I enhanced this on my fork: https://gist.github.com/rubo77/6821632

• no need for eval(), I use the original parse_str() on each part of the query, so no need for josh's fix
• the result created in the second parameter like the behaviour in parse_str(): http://php.net/manual/function.parse-str.php
• fixed the behaviour on empty strings

Alternative without eval: https://github.com/boryo/php_parse_str