Dizkus

It was pointed out to me that the module I developed tRSSNews is placing Smarty temp files in ./tmp instead of pnTemp. The temp files are not being deleted either. This is leading to the tmp directory continuously growing. I've been unable to track down when it's happening exactly, but there are no variables overwriting the pnTemp variable. It seems to be happening with PN750 and up. BTW the files appear to be the htm templates and the PHP source code (ie. pnadminapi.php) just with tmp names. Nothing seems to be modified. Does anyone have a clue why this might be happening, or suggestions of where to start looking. I'm using the latest PostNuke .761 and the pnTemp variable is set in config.php. This is not a fluke as it seems to be happening on other's installs.

Thanks for any help.
Shiner

PS. One of the tmp files on another persons setup appears as:

This does not occur with my setup.

**Update** I did notice that the versions of the files appearing in ./tmp are old versions, like really old. Have no clue where they are coming from.

I take it that your module uses pnRender rather than its own Smarty installation?

--
Regards,
Simon

itbegins.co.uk - Zikula Consulting

Please read the Support Guide

Yah it does use pnRender and not it's own Smarty implementation. I did check the temp variable in Smarty and it says it's writing to pnTemp/pnRender_compiled and I varified this. What's really interesting is that the temp files that are appearing are from versions of the software that in some cases are almost 2 months old. None of the installs of tRSSNews are using these old versions. The source is available at http://www.trever.org and the files that are showing up are both the PHP files and htm (templates)

Shiner