:) I finally got it working!
Thanks for pointing me to FeedX - the support thread there tipped me off to the problem. It seems that the snippet parsing can’t handle complex URLs as parameters. So you need to replace the "?" ,"=" and "&" with something else, and then when you are handling the URL, you need to restore these values.
FeedX chose to use their own string substitution values, (|xq| for Questionmark, |qe| for Equals, and |qa| for Ampersand), which are easy to remember, but not standard.
Instead, I escape my URL before putting it in the snippet. One quick way to do this is to copy your complex URL to the clipboard, then in your favorite browser’s address type:
javascript:escape("YOUR-URL-HERE");
(For this to work, you need to make sure that your pasted URL is surrounded by quotes.)
When you hit return, the value of the escaped URL is displayed (all the ?’s changed to %3F, all the spaces changed to %20, etc.) Now use this escaped URL in your snippet.
The snippet needs to be modified to unencode the URL.
In the case of the XSLT snippet, I modified the snippet to decode the URL right before the CURL call. So in the XSLT Snippet, I added the following line , just before "//Create Curl Session"
$xmlURL = urldecode($xmlURL);
And now, everything seems to work!
It would be nice if all the snippets standardized on encoding URLS, so that there would be less to remember when moving among snippets. I suggest that standard URL encoding and decoding would be a best practice...
Anyway, hope my exploration of this, and suggested patch for XSLT help other Feed Readers and XML digesting folks.
Cheers.
Tom
Yeah!!) 