The following warnings occurred: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Warning [2] Undefined array key "avatartype" - Line: 783 - File: global.php PHP 8.1.28 (Linux)
|
error [smarty.include]: failed to open - Printable Version +- Form Tools (https://forums.formtools.org) +-- Forum: Form Tools (https://forums.formtools.org/forumdisplay.php?fid=1) +--- Forum: Installation (https://forums.formtools.org/forumdisplay.php?fid=4) +--- Thread: error [smarty.include]: failed to open (/showthread.php?tid=722) |
error [smarty.include]: failed to open - jwalter - May 28th, 2010 I have been using FormTools for several years and really like. Ihave just updated to Version 2. When I go to the browser to install the new version I get the following error: Warning: Smarty::include(\formtools\themes\default\cache\%%5D^5D9^5D971EF4%%index.tpl.php) [smarty.include]: failed to open stream: No such file or directory in ... Warning: Smarty::include() [function.include]: Failed opening \formtools\themes\default\cache\%%5D^5D9^5D971EF4%%index.tpl.php' for inclusion ... Would appreciate any help you can provide. RE: error [smarty.include]: failed to open - variationdesign - May 29th, 2010 Hello there, This is a file permission problem to do with the cache folder in the themes directory. If you are using the default theme, as it appears to be in the above error code, you need to navigate to themes\default and give the cache folder write permissions. Should work after that Seth RE: error [smarty.include]: failed to open - jwalter - May 29th, 2010 Thank you Seth, Still getting the error. I have checked the default and cache directories and both have 777 permissions. The files in these directories have 666 permissions. We are using php running on IIS, could this be a problem? Would appreciate help on how to fix this. thanks, RE: error [smarty.include]: failed to open - Ben - Jun 1st, 2010 Hi jwalter, Yes, that may be a problem. Try deleting the entire contents of the cache folder and log in again. I suspect that may fix it. - Ben |