[nothingman]

Now, I can't sit in front of my site all the time and then wait for this parse error to happen (..and well, log on to my ftp, delete the files in the templates_c folder and then apologize to my users about the error.)

This is what I'm talking about:

Parse error: syntax error, unexpected $end in /home/userdir/public_html/templates_c/c_ef20b2b5fff08f636a080a9108ff9329.php on line 134

The only solution that I've come across from the forums is to delete everything under the templates_c folder.

• What are you guys doing about it?
• Is there an alternative available (like say, create a cron job?)
• If you folks are using a cron job, how are you going about it (i.e. to all the files of a particular folder?)

Any help or insights into this issue?
Thanks in advance.

[netfreak]

Try deleting all files under "template_c" directory.
Don't worry those are temporary files.

[nothingman]

Originally Posted by netfreak

Try deleting all files under "template_c" directory.
Don't worry those are temporary files.

Thanks netfreak but I'm aware of that solution.

When the no. of concurrent users on my site goes beyond, say 26 people, this parse error happens constantly. Some days back I was on vacation and to my horror, the site was down for a whole week. Why? because of this parse error.

I believe there has to be a 'better' solution than just 'manually' deleting all the files under the "templates_c" folder/directory on a periodic basis.

[catchpen]

Sometimes this helps
When you get the parse error, refresh browser and if it's the identical error with the same template_c file and identical line #134 again, look at that file in notepad or html editor sometimes it will give some more info where it's coming from.

[nothingman]

Originally Posted by catchpen

Sometimes this helps
When you get the parse error, refresh browser and if it's the identical error with the same template_c file and identical line #134 again, look at that file in notepad or html editor sometimes it will give some more info where it's coming from.

Thanks catchpen. It's the identical line most of the time. Could you elaborate on how that'd help and what needs to be done? (Can't paste the contents of the the said line as I can't reproduce it on my site at the moment.)

Thanks again.

[catchpen]

I'm no coder but try to look at line # 134 in c_ef20b2b5fff08f636a080a9108ff9329.php (the file you listed in your post) with notpad or a html editor.
- I've noticed the temp files in the templates_c folder have recognizable code from one of the php files in your Pligg root since that's where they're created from. Maybe it will point to where the problem is coming from.

[nothingman]

Thanks catchpen. I'm not a coder myself hence this thread. I was hoping that our pligg masters would answer this one Not being a brat here, but as a question to our pligg developers, will this be issue be fixed in future releases?