Task #27941

Add check in reports module concerning outdated localconf.php settings

Added by Oliver Hader about 8 years ago. Updated about 4 years ago.

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

0%

TYPO3 Version:
4.6
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Since TYPO3 4.6 is a rebase there are some settings that were valid in the past in localconf.php but have been removed in between.
Instead of checking for those settings and putting to the deprecation log for every request, it would be better to have a notification about that in the reports module.


Related issues

Related to TYPO3 Core - Bug #27927: Remove publish.php Closed 2011-07-06
Related to TYPO3 Core - Task #26519: Language handling: splitLabels and locallang.php should be removed Closed 2011-04-29

History

#1 Updated by Xavier Perseguers about 8 years ago

  • Target version changed from 1281 to 4.6.0-beta1

#2 Updated by Xavier Perseguers about 8 years ago

  • Target version changed from 4.6.0-beta1 to 4.6.0-beta2

#3 Updated by Xavier Perseguers almost 8 years ago

  • Target version changed from 4.6.0-beta2 to 4.6.0-beta3

#4 Updated by Oliver Hader almost 8 years ago

  • Target version changed from 4.6.0-beta3 to 4.6.0-RC1

#5 Updated by Xavier Perseguers almost 8 years ago

  • Target version changed from 4.6.0-RC1 to 4.6.0

#6 Updated by Chris topher almost 8 years ago

  • Target version changed from 4.6.0 to 4.6.1

#7 Updated by Chris topher over 7 years ago

  • Target version changed from 4.6.1 to 4.6.2

#8 Updated by Xavier Perseguers over 7 years ago

  • Assignee deleted (Oliver Hader)
  • Target version deleted (4.6.2)

#9 Updated by Wouter Wolters over 4 years ago

  • Status changed from New to Needs Feedback

The new Install Tool is able to remove this entries now.
If I'm correct this solved now.

#10 Updated by Alexander Opitz about 4 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Also available in: Atom PDF