Bug #40161
Task #40095: Move core to namespaces
Add Tx_Scheduler_AdditionalFieldProvider to mapping
| Status: | Rejected | Start date: | 2012-08-25 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 100% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 6.0 | Is Regression: | ||
| PHP Version: | Sprint Focus: | |||
| Complexity: |
History
#1 Updated by Christian Kuhn almost 3 years ago
Using the old interface must still work!
#2 Updated by Steffen Gebert almost 3 years ago
- Status changed from New to Accepted
#3 Updated by Christian Kuhn almost 3 years ago
it is in the mapping, but there seems still to be a problem, it seems to work on non case sensitive filesystems, but doesn't on case sensitive systems. example extension to reproduce is enetcache: just install and then try to add a task.
Fatal error: Declaration of tx_enetcache_task_DropTags_AdditionalFieldProvider::getAdditionalFields() must be compatible with that of TYPO3\CMS\Scheduler\AdditionalFieldProviderInterface::getAdditionalFields() in ....
#4 Updated by Nicole Cordes almost 3 years ago
I got this one as well and Thomas and I discovered it is related to an outdated PHP version ( < 5.3.8).
We have to develop some workaround for lower versions which we have to support as well (current official Debian version is 5.3.3)
#5 Updated by Christian Kuhn almost 3 years ago
- Status changed from Accepted to Rejected
- % Done changed from 0 to 100
Not valid anymore, solved with a compat layer for low 5.3 php versions.