I don’t think this is possible. LiveDocx works on the basis of placeholder fields being replaced with content at runtime. Obviously without a template there wouldn’t be any placeholders to replace. Perhaps there are other libraries that allow you to create word documents from scratch but it’s not what LiveDocx is about.

No, I haven’t done anything with the AJAX API but would be interested in looking into it. Do you know of any resources that illustrate how to use it? Does the AJAX API search the main Google index? One of the advantages of the Custom Search Engine API is that Google builds a customised index of the site. Still, I believe in using the right tools for the job and for another client that may well be the AJAX API.

You mention that the Google API key has a cost. Have you done anything with the Google AJAX Search (which appears to be free)?

A lot better then filtering them on demand. this will disable them a lot more globally.

Anyways a nice example of using a reference closure recursion.

Thanks for the comment. I should have made it clearer in the post that the code is merely an example for the technique. I used the magic_quotes example because a) it’s the one that came to mind at the time and b) my hosting company has that directive enabled. Unfortunately although magic_quotes are deprecated I can’t see them disappearing any time soon, at least not until every hosting company and server is running PHP 6 (or whatever the next version is going to be called). Personally, I can’t wait for the time when magic_quotes are removed from PHP entirely.

Thanks for the info about keys and magic_quotes-I wasn’t aware of that. I’m not sure if I’m too worried about that though. I can’t think of a time when I’ve written a POST, GET or Cookie key that contained characters that would need to be escaped by magic_quotes. One could argue that there’s a potential security vulnerability since there’s nothing to stop an attacker submitting arbitrary key => value pairs. I would argue though that it’s the job of the developer to only work with parameters that they’re expecting in the request, filtering these in the strongest ways possible. For me the code in the post gives a good start by removing any slashes before any parameters in the request are filtered.

Please also be adviced that besides the root keys al keys should go through stripslashes as well!

See the manual: http://www.php.net/manual/en/security.magicquotes.disabling.php