epogue

This is so awesome! Thank you!

Hey,   I was experimenting with workflows that allowed "drilling down" into an result to provide more options, and here's what I came up with.   Firstly, a workflow that uses omdbapi.com to search for movies, actioning a result shows you more information and actions.   Download: here or via AlfPT     As a second workflow using this I built an alternative client workflow to Tom Hunt's Alfred Workflow repository. It has some performance improvements over the "official" AlfPT workflow, and a few extras like updating all workflows, uninstalling and opening workflow folder from within the workflow.    
Download: here or via AlfPT

It's no problem. On line 30 in extension_utils.php, replace $c->addChild( $key, $b[$key] ); with
$c->$key = $b[$key];  
 
Then, in search.php, on lines 38 - 41, remove the methods (utf8_encode and htmlentities) wrapping the attribute calls. For instance, instead of 'uid' => utf8_encode ( htmlentities ( $bookmark->url ) ), it should read:
'uid' => $bookmark->url,

It's no problem. On line 30 in extension_utils.php, replace $c->addChild( $key, $b[$key] ); with
$c->$key = $b[$key];  
 
Then, in search.php, on lines 38 - 41, remove the methods (utf8_encode and htmlentities) wrapping the attribute calls. For instance, instead of 'uid' => utf8_encode ( htmlentities ( $bookmark->url ) ), it should read:
'uid' => $bookmark->url,

I found a possible fix that seems to be holding up to whatever weird entities I throw at it. I looked it up, and apparently SimpleXML will automatically do all the escaping it needs when using the assignment operator instead of addChild. Therefore, I tweaked the arrayToXml() function in extension_utils, replacing:
 
$c->addChild( $key, $b[$key] );  
with:
 
$c->$key = $b[$key];  
and deleted the wrapping utf8_encode(htmlentities()) calls in search.php.
 
Hope this works for you guys!