Forum Moderators: coopster
What i understand (I am not sure whether i understood correct) from the thread is I will have to either rename all .tpl file to .tpl.php or edit .htaccess file to handle the file the way I want it to be handled. Renaming is out of the question as there are more than 1000 such files.
So, what lines i am suppose to add in htaccess file? where to find httpd.conf file?
details:
server: 2.2.11 (Unix)
PHP version: 5.2.9
thank you.
Problem is i am seeing two percentage signs (%%) before and after a sentence.
This sounds like a different problem to the problem in your thread title: (?)
php code in .tpl file being displayed as text
The link you give partly relates the problem in your thread title, not necessarily to double percent signs. That link talks about securing template files so that PHP code remains hidden if the template engine is bypassed, ie. the template files are accessed directly by the browser. If the site is accessed in the way it is intended then this is should not a problem (depending on how the templates are loaded by your script). Are you having fundamental problems with your PHP script, or are you trying to improve the security of your site?
%% are more likely to delimit fields in your template. Your template engine (ie. php script) would need to parse your template and replace these. PHP code is more usually delimited by <?php ... ?> Is this what you are seeing output to the browser?
Even after installtion percent signs still can be seen in template (before and after each visible text).
What do you think it should be?
What does your PHP script expect the template variables to be delimited by? ie. %%VARIABLE%% (two percent signs)? This might be customisable in the script. What does your template source file look like at the point you are seeing "%%" in the output - perhaps you could post this?
Are other template variables being parsed/replaced OK? What is different about this one?
Presumably you don't get any errors output?
Unfortunately, without delving through the code and getting some idea of what's going on the problem could be anything!? Unless, by chance, someone reading this has used the same script and experienced the same problem...?