Project

General

Profile

Actions

Bug #46642

closed

Fatal error: Cannot unset string offsets in typo3/sysext/em/classes/tools/class.tx_em_tools.php on line 382

Added by Peter Linzenkirchner about 11 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2013-03-25
Due date:
% Done:

100%

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

Description

when uploading an extension to TER (TYPO3 4.5) the $EM_CONF[$_EXTKEY] = array becomes wrong:

original php code:

$EM_CONF[$_EXTKEY] = array (
    //snip
    array (
        'depends' => array (
            'typo3' => '4.5.0-6.0.99'
        ),
        'conflicts' => array(

        ),
        'suggests' => array (

        ),
    ),
    //snip

becomes after uploading:

    array (
        'depends' => 
        array (
            'typo3' => '4.5.0-6.0.99',
            '' => '',
        ),
        'conflicts' => '',
        'suggests' => 
        array (
        ),
    ),

which leads to the following error in the extension manager of TYPO3 4.5.x:

Fatal error: Cannot unset string offsets in typo3/sysext/em/classes/tools/class.tx_em_tools.php on line 382
I had to edit the em_conf.php manually in order to get rid of this error in the backend.


Files

46642.diff (737 Bytes) 46642.diff Franz Holzinger, 2013-07-26 17:36

Related issues 2 (0 open2 closed)

Has duplicate TYPO3 Core - Bug #46611: 4.5 EM crashes, if ext_emconf entry is string instead of arrayClosed2013-03-23

Actions
Has duplicate TYPO3 Core - Bug #44282: EM: fatal error if 'conflicts' is empty string in stead of arrayClosed2013-01-03

Actions
Actions #1

Updated by Daniel Hürtgen almost 11 years ago

Same here ... also fixed by edit ext_emconf.php manually.

Actions #2

Updated by Franz Holzinger over 10 years ago

Still present in TYPO3 4.5.28

Fatal error: Cannot unset string offsets in /var/www/user/typo3_src-4.5.28/typo3/sysext/em/classes/tools/class.tx_em_tools.php on line 390

Use this patch to get the Extension Manager running again.

Actions #3

Updated by Franz Holzinger over 10 years ago

Actions #4

Updated by Gerrit Code Review over 10 years ago

Patch set 1 for branch TYPO3_4-5 has been pushed to the review server.
It is available at https://review.typo3.org/22656

Actions #5

Updated by Gerrit Code Review over 10 years ago

Patch set 1 for branch TYPO3_4-7 has been pushed to the review server.
It is available at https://review.typo3.org/22657

Actions #6

Updated by Michael Stucki over 10 years ago

I investigated the problem and have submitted patches to fix the issue in 4.5 and 4.7.
Interestingly, the problem does not occur in 6.0+ versions because the new extension manager contained the fix since the beginning.

Actions #7

Updated by Michael Stucki over 10 years ago

  • Project changed from 336 to TYPO3 Core

Moving to TYPO3 CMS: Core

Actions #8

Updated by Michael Stucki over 10 years ago

  • Status changed from New to Accepted
  • Assignee set to Michael Stucki
  • TYPO3 Version set to 4.5
Actions #9

Updated by Michael Stucki over 10 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100
Actions #10

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF