Instead, the code should call the “auto” function, as follows:

FLIR.init( { path: ‘/path-to-flir/’ } );
FLIR.auto();

This is the code used in the older documentation, and still seems to be correct.

It’s also not necessary to nest an ID of “permalink” inside the heading tags when creating definitions in the CSS. Thus,
h1#permalink {
only needs to be:
h1 {

http://localhost/facelift/generate.php?text=hello

In chrome, the image gets created in the cache folder, but I get a broken image on the screen. When I run in FF3, I get a message that the image couldn’t be displayed because it contained errors.

The security issue is a problem though – I suspect the issue is that anyone could hit “http://www.yourwebserver.com/facelift/generate.php?text=some%20text%20heading” and be creating all the fancy headlines they want for their site without having any server processor overheads.

That’s a major problem in my eyes.

Unanswered questions:

-Is GD truly required (not clear from Corey vs. this tutorial)
-Where is GD placed (directory)
-Any FLIR files that need to be updated to reflect GD?

As I said, even without GD, I can’t get the three different fonts, or even one of them to replace some simple through I did on a page, then included the recommended javascript.

For now, I am not sold….

Quote from Clarklab on http://css-tricks.com/video-screencasts/54-introduction-to-flir/

“Here at work I used FLIR in a project very heavily once only to have our security team come two days before launch and veto it. Apparently its not secure at all, the image paths generated have the full script parameters displayed, and there is nothing stopping someone from just blasting your script, over and over creating tons of server processing and filling your cache…”

I’d love to use it on my site but this sounds very bad!
Can you confirm/deny this claim?

Tell people they need to CHMOD their Cache directory.

Nobody likes an incompete install-guide.