Project

General

Profile

Actions

Bug #25335

closed

Make TYPO3 free of NOTICE errors

Added by Xavier Perseguers about 13 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-06-06
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
TYPO3 Version:
4.6
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Running TYPO3 with PHP NOTICE errors on is simply not possible as there are far too many errors reported.

This bug entry serves as umbrella for cleanup within TYPO3 Core.

Resolution should target PHP5.3.

(issue imported from #M17962)


Subtasks 2 (0 open2 closed)

Bug #27230: cmpIPv4: prevent E_NOTICE, cleanup compare, testcasesClosedStefan Neufeind2011-06-06

Actions
Bug #27250: Get rid of error_reporting() at various places in the sourceClosed2011-06-06

Actions

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #31461: The Big Cleanup 4.7Closed2012-02-192012-02-20

Actions
Actions #1

Updated by Ernesto Baschny about 13 years ago

  • TYPO3 Version changed from 4.5 to 4.6
  • PHP Version deleted (5.3)
Actions #2

Updated by Chris topher over 12 years ago

  • Target version changed from 4.6.0 to 4.6.1
Actions #3

Updated by Chris topher over 12 years ago

  • Target version changed from 4.6.1 to 4.6.2
Actions #4

Updated by Xavier Perseguers about 12 years ago

  • Target version deleted (4.6.2)
Actions #5

Updated by Alexander Opitz almost 10 years ago

  • Is Regression set to No

What's the state of this issue?

Actions #6

Updated by Xavier Perseguers almost 10 years ago

This is an umbrella ticket and one of its children is not closed.

However, I'd say that in latest versions of TYPO3 and furthermore with the introduction of the "Developer context", I don't have any problem anymore.

Actions #7

Updated by Alexander Opitz over 9 years ago

Hi Xavier,

the childs are resolved, so can we close this umbrella?

Actions #8

Updated by Xavier Perseguers over 9 years ago

  • Status changed from New to Resolved
Actions #9

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF