Bug #14632
closedParse error with border.html
0%
Description
Parse error: parse error, unexpected T_STRING in /srv/www/htdocs/webxx/www/TYPO3core/typo3/border.html on line 1
I think it's better to create a file like border.php:
echo '';
echo '';
echo '<!DOCTYPE html ';
echo ' PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"';
echo ' "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">';
echo '<html>';
echo ' <head>';
echo ' <meta http-equiv="Content-Type" content="text/html; charset=utf
echo ' <title>Border between Navigation and List frame in TYPO3</title
echo ' </head>';
echo ' <body background="gfx/border_back.gif">';
echo ' </body>';
echo '</html>';
?>
I think it's the same like the postings from Karsten Hachmeister (11.12.2003) and Michael Stucki (17.02.2004):
"Hi,
just installed it.
If I click at 'Task center' and then for example at 'List', normally I get back
to the pagetree. This works for the first time, but if I do the same a second time I still see the 'Task overview' and not the page tree.
The border.html file in the typo3 folder gives a parse error on my system. This is not really a bug, because short_open_tag in my php.ini is activated. For a quick solution I echo out the xml definitions.
--
Karsten Hachmeister
##
Looks like you parse HTML files as PHP (=> httpd.conf) and have short-tags enabled (=> php.ini).
Michael Stucki"
(issue imported from #M929)
Updated by Rupert Germann over 19 years ago
The suggestion to set short_open_tag = Off in php.ini is not usable on some cases because it can be needed by other software on the server. f.e. if you have confixx installed that's not possible because it needs short_open_tag = On
A solution could be to disable short_open_tag in .htaccess but this file is not enabled by default and possibly the server is configured not to accept .htaccess directives.
So IMO converting the file to php and echoing out its contents should work in all cases without the need of changing to webserver configuration.
Updated by Karsten Dambekalns over 19 years ago
But the error is not only caused by short_open_tag being on, but also by the fact that HTML files are parsed as HTML - thus causing a "bug" that would be triggered by whatever (X)HTML file containing a XML declaration.
To me it seems as if this is a "bug" in the server configuration (and if confixx need a short open tag it should be dumped).
Updated by Karsten Dambekalns over 19 years ago
This is (sort of) a duplicate of #14145 (which has other implications about MSIE as well, but the bottom line (XHTML, short_open_tag, parsing HTML files) is the same.