Smarty_v2 Compile Errors

[leelee23]

Hi there,

 

My active site appears to keep going down, whilst all that is shown when going on the domain is a blank page. I've just scrawled through the recent error log and there appears to be an error within the tools/smarty_v2/compile/ folder. For example:

 

[17-Mar-2012 15:11:00] PHP Parse error: syntax error, unexpected ',' in /home/yourbran/public_html/tools/smarty_v2/compile/%%7A^7A3^7A3DC106%%blocksearch-top.tpl.php on line 101

[17-Mar-2012 15:11:01] PHP Parse error: syntax error, unexpected $end in /home/yourbran/public_html/tools/smarty_v2/compile/%%56^562^56234490%%header.tpl.php on line 69

[17-Mar-2012 15:11:22] PHP Warning: Unexpected character in input: ''' (ASCII=39) state=1 in /home/yourbran/public_html/tools/smarty_v2/compile/%%FB^FBE^FBE0B8DC%%blockcms.tpl.php on line 51

[17-Mar-2012 15:11:22] PHP Parse error: syntax error, unexpected '-', expecting T_STRING or T_VARIABLE or '$' in /home/yourbran/public_html/tools/smarty_v2/compile/%%FB^FBE^FBE0B8DC%%blockcms.tpl.php on line 51

[17-Mar-2012 15:11:30] PHP Warning: Unexpected character in input: ''' (ASCII=39) state=1 in /home/yourbran/public_html/tools/smarty_v2/compile/%%FB^FBE^FBE0B8DC%%blockcms.tpl.php on line 51

 

This happened first of all the other day after I had done a new feed generation of Google Base v0.7.3.5 but once I re-made the feed after I'd noticed the error, then this resolved the problem.

 

3 days later (after having not modified anything within the site at all) the problem appears to be back.

 

I just deleted all of the content in the tools/smarty_v2/compile/ folder and the site seems to be functional once again, but having said that - I'm concious that the site will go down again, similar to the previous resolve.

 

Any ideas of why this is happening? And how I can go about stopping this from happening again?

 

 

Cheers,

 

Lee

[phrasespot]

Why Smarty 2? Use Smarty 3 unless you have a specific reason not to.

[leelee23]

My theme seems to struggle with Smarty 2... i.e it doesn't actually load!

 

Either way, I discovered the issue... I was over the limit on my webspace allowance and for some reason when the site was caching the size kept it creeping over the limit and causing the error. I've made some space on the server, and the site seems to be working well (touch wood!)