Rokk Media Posted December 22, 2008 Share Posted December 22, 2008 Trying to update a client's installation from 1 to 1.1 running into the following and can't find a solution - help!!:Warning: Smarty::include(C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop/tools/smarty/compile\%%^FD4^FD4FA444%%header.tpl.php) [smarty.include]: failed to open stream: No such file or directory in C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop\tools\smarty\Smarty.class.php on line 1259Warning: Smarty::include() [function.include]: Failed opening 'C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop/tools/smarty/compile\%%^FD4^FD4FA444%%header.tpl.php' for inclusion (include_path='.;./includes;./pear') in C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop\tools\smarty\Smarty.class.php on line 1259Warning: Smarty::include(C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop/tools/smarty/compile\%%^F9A^F9AF6B43%%index.tpl.php) [smarty.include]: failed to open stream: No such file or directory in C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop\tools\smarty\Smarty.class.php on line 1259Warning: Smarty::include() [function.include]: Failed opening 'C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop/tools/smarty/compile\%%^F9A^F9AF6B43%%index.tpl.php' for inclusion (include_path='.;./includes;./pear') in C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop\tools\smarty\Smarty.class.php on line 1259Warning: Smarty::include(C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop/tools/smarty/compile\%^04F^04FC9095%%footer.tpl.php) [smarty.include]: failed to open stream: No such file or directory in C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop\tools\smarty\Smarty.class.php on line 1259Warning: Smarty::include() [function.include]: Failed opening 'C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop/tools/smarty/compile\%^04F^04FC9095%%footer.tpl.php' for inclusion (include_path='.;./includes;./pear') in C:\Inetpub\vhosts\clientshop.co.uk\httpdocs\shop\tools\smarty\Smarty.class.php on line 1259OK - turns out that there are a bunch of temp files in the Compile folder within Smarty (Tools) which also need to be moved to the same place in the new installation. Having done that those errors have disappeared! Hope this helps anyone else with similar problems. Link to comment Share on other sites More sharing options...
Rokk Media Posted December 22, 2008 Author Share Posted December 22, 2008 Any ideas at all? Link to comment Share on other sites More sharing options...
Dave Egerton Posted December 22, 2008 Share Posted December 22, 2008 Hi RokkI don't really have any idea, but did you make the files and folders that need to be: writeable (like with a new install instruction in Wike)I did an upgrade on my local Windows PC, but its runs EasyPHP...Its just a thought really Link to comment Share on other sites More sharing options...
Rokk Media Posted December 22, 2008 Author Share Posted December 22, 2008 Hi - I usually work with LAMP installations, but my understanding is that this is set within IIS and you shouldn't need to set them manually after that (in fact you can't). The previous installation version 1.0 worked fine from the outset. Link to comment Share on other sites More sharing options...
Rokk Media Posted December 23, 2008 Author Share Posted December 23, 2008 Does anyone know how to force Smarty to recompile templates? I'm still getting missing template errors - not sure if that's what's needed, but they didn't exist in the old compile folder. Link to comment Share on other sites More sharing options...
bykrmom Posted December 23, 2008 Share Posted December 23, 2008 '$force_compile' is available as a variable built-in to smarty. But rather than using that, you can use '$compile_check'. This tells smarty to see if there are changes to the templates and to recompile if the time stamps are different. Using the $force_compile would slow you down drastically, but would work. The value of $compile_check should be set to TRUE to use it. Hope that helps you out? Link to comment Share on other sites More sharing options...
Rokk Media Posted December 23, 2008 Author Share Posted December 23, 2008 Thanks - the problem was even simpler than that - the compile folder just needed permissions set properly (in IIS) and all worked a treat :-)The entire update process took a day which is a bit painful - it would be good if this could somehow be improved, but while modification of modules etc is unavoidable I guess it's just' par for the course. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now