Hi geekster,
The phpthumbof output filter is operating on the processed output of your TV. That is to say, since you are using the "image" output type, the entire html image tag gets sent to phpthumbof. Phpthumbof expects a path to a file, not an html tag, therefore it is failing.
Two options immediately come to mind:
1) change the TV output type back to Default, so phpthumbof has a path to operate on (then you would have to place the image tag html into your template)
2) write a custom output filter snippet to "wrap" phpthumbof functionality, but with additional smarts to parse the html image tag that the TV is creating, find the image path and send it to phpthumbof, then inject the thumbnail path back into the html image tag
A third option has occurred to me but I have never tried this:
3) Set your image TV output type to Default; create another TV (named for example "featurethumbwrapper"), just a regular text type but make it's default value
and set it's output type to image. Then use
in your template and you should end up with the html image tag containing the path to the thumbnail. (You could also achieve something similar with a Chunk as your html image tag template, and setting the
TV as a property in the Chunk tag, e.g.
[[$myImageTag? &thumb=`[[*featurethumb]]`]]
where your myImageTag Chunk is something like <img src="[[+thumb]]"> .)
Also, looking at your example, depending on how many TVs your aggregated Templates have, you may want to take advantage of the includeTVList and processTVList parameters of getResources so that you're not processing TVs that you aren't using in your getResources templates. (TV processing is a fairly expensive operation.)
Hope this helps to get you back on track with Revolution.
[ed. note: netProphET last edited this post 11 years, 7 months ago.]