http://blog.mirthlab.com/2008/08/18/parsing-jquerys-sortableserialize-method-with-php-and-symfony/ fortune favors the bold Tue, 06 Jan 2009 10:33:51 +0000 http://wordpress.org/?v=2.7 hourly 1 http://blog.mirthlab.com/2008/08/18/parsing-jquerys-sortableserialize-method-with-php-and-symfony/comment-page-1/#comment-994 Nick Mon, 03 Nov 2008 21:02:01 +0000 http://blog.mirthlab.com/?p=48#comment-994 I concur. I concur.

]]> http://blog.mirthlab.com/2008/08/18/parsing-jquerys-sortableserialize-method-with-php-and-symfony/comment-page-1/#comment-376 openmind » Blog Archive » PHP: url_string_to_array Fri, 12 Sep 2008 21:03:46 +0000 http://blog.mirthlab.com/?p=48#comment-376 [...] There’s really no easy way to pass jQuery’s sortable serialize method output to PHP; Mark Quezada has one elegant solution. The following code owes its thesis to his post; this builds on the idea [...] [...] There’s really no easy way to pass jQuery’s sortable serialize method output to PHP; Mark Quezada has one elegant solution. The following code owes its thesis to his post; this builds on the idea [...]

]]> http://blog.mirthlab.com/2008/08/18/parsing-jquerys-sortableserialize-method-with-php-and-symfony/comment-page-1/#comment-259 Mark Quezada Tue, 19 Aug 2008 10:07:02 +0000 http://blog.mirthlab.com/?p=48#comment-259 @Mike: Yup, that's the way I ended up using it. Seems strange and wrong to me that the default usage expands all variables into the local scope. Anyway, I've updated the article. Thanks! @Mike: Yup, that’s the way I ended up using it. Seems strange and wrong to me that the default usage expands all variables into the local scope. Anyway, I’ve updated the article. Thanks!

]]> http://blog.mirthlab.com/2008/08/18/parsing-jquerys-sortableserialize-method-with-php-and-symfony/comment-page-1/#comment-255 Mike Nolan Tue, 19 Aug 2008 07:54:14 +0000 http://blog.mirthlab.com/?p=48#comment-255 It's probably safer to provide the second parameter to parse_str() and access from that array rather than creating variables in the local scope. It’s probably safer to provide the second parameter to parse_str() and access from that array rather than creating variables in the local scope.

]]>