ID: 14623
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Strings related
Operating System: linux
PHP Version: 4.0.6
Old Assigned To: elixer
Assigned To: 
New Comment:

<?

$s = "
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
... repeat this for about 110 lines of 80 'x'-es
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
";

?>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>
<head>
        <title>Failing get_meta_tags</title>
  <META NAME="subject" CONTENT="mySubject">
  <META NAME="keywords" CONTENT="myKeywords">
  <link rel="stylesheet" href="mysheet.css">
</head>

<body>
GET_META_TAGS:
<?
print_r( get_meta_tags( $HTTP_SERVER_VARS["PATH_TRANSLATED"]));
?>
</body>
</html>


Previous Comments:
------------------------------------------------------------------------

[2001-12-20 19:34:44] [EMAIL PROTECTED]

Can you please provide me with a small example of a file that get_meta_tags is failing 
on? The only time I am seeing this fail is if the text "</head" appears in the 
"working code" that you mention.

Sean

------------------------------------------------------------------------

[2001-12-20 10:59:01] [EMAIL PROTECTED]

get_meta_tags() seems to look only in the beginning of a file, meaning that e.g. if 
there is a lot of PHP code before the HTML header it will return nothing ...

Tested using get_meta_tags() on local files with about 9000 characters of PHP code 
before HTML HEADER.

Might be by design (speed), but then a warning is needed in doc: when adding working 
code, things (get_meta_tags()) stop working ...

Workaround: if possible move code after header or if not include a file :(


------------------------------------------------------------------------



Edit this bug report at http://bugs.php.net/?id=14623&edit=1


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to