Project

General

Profile

Actions

Bug #15632

closed

Backend: Parsing error in list view for image/text when using a colon in the text

Added by Gerald Schwarz almost 19 years ago. Updated over 17 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2006-02-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.0
PHP Version:
4
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

-After upgrading to typo 4beta2 i realized a parsing error in the backend
-the error occures only in the list-view under the following circumstances:
1)using a text/image -contentelement and
2)the text of the img/text element ends with a colon (:)

the error disappears, when i erase the colon. See the uploaded pictures to see the diference.

the Text message is:

Warning: parse_url(Favicon:): Unable to parse url in /typo3_src-4.0beta2/typo3/class.db_list.inc on line 602

Warning: Cannot modify header information - headers already sent by (output started at /typo3_src-4.0beta2/typo3/class.db_list.inc:602) in /typo3_src-4.0beta2/typo3/template.php on line 601

(issue imported from #M2573)


Files

warning_parsing_error.gif (22 KB) warning_parsing_error.gif Administrator Admin, 2006-02-15 19:44
Actions #1

Updated by Gerald Schwarz over 18 years ago

the same error further exists in 4.0beta3

Actions #2

Updated by Wolfgang Klinger over 18 years ago

I cannot reproduce this with PHP 4.4.1,
what PHP version is installed on your server?

We might set a @ in front of the parse_url call to avoid this problem though.

Actions #3

Updated by Gerald Schwarz over 18 years ago

Php version: 4.3.3

Actions #4

Updated by Romain Fougier about 18 years ago

Hi,
Today, Typo3 is now in version 4.0.1 and the problem continues to occur.
It would be judicious to add the '@' in front of the function "parse_url()" in "class.db_link.inc" definitively ( for php 4.3 users ).

Actions #5

Updated by Michael Stucki about 18 years ago

This is a bug in PHP, see http://bugs.php.net/bug.php?id=25800:
PHP < 4.3.4 thinks that the colon is used to specify a port. Since the port is missing, it fails with an error.

A workaround could be to add a @ in front of the call, but on the other hand this would suppress all other, probably valid error messages, too.

Recommendation: Upgrade to a more recent PHP version or disable display_errors in php.ini.

- michael

Actions

Also available in: Atom PDF