Issue Bug Closed

#17178Extensions with dependencies - datatransfer did not sucseed

Martin Holtz 04/02/07, 11:01 updated 08/06/10, 13:17

Description

I install cal and i got the message “Extensions suggested by extension “cal”“

If i “Import now (opens a new window)” i got that error:

“Error: The datatransfer did not succeed. The T3X file could not be fetched. Possible reasons: network problems, allow_url_fopen is off, curl is not enabled in Install tool.”

But if i install the extension – for example captcha – there is no error.

i use typo3 4.1 i believe it works before with 4.1…?

I ot that Error Messages:

Warning: array_keys(): The first argument should be an array in /data/htdocs/typo3_src-4.1/typo3/mod/tools/em/class.em_index.php on line 1718
Call Stack
  1. Function Location
    1 {main}() /data/htdocs/typo3_src-4.1/typo3/mod/tools/em/index.php:0
    2 ux_sc_mod_tools_em_index->main() /data/htdocs/typo3_src-4.1/typo3/mod/tools/em/index.php:54
    3 ux_sc_mod_tools_em_index->importextfromrep() /data/htdocs/typo3_src-4.1/typo3/mod/tools/em/class.em_index.php:534
    4 array_keys () /data/htdocs/typo3_src-4.1/typo3/mod/tools/em/class.em_index.php:1718
Warning: end(): Passed variable is not an array or object in /data/htdocs/typo3_src-4.1/typo3/mod/tools/em/class.em_index.php on line 1719
Call Stack
  1. Function Location
    1 {main}() /data/htdocs/typo3_src-4.1/typo3/mod/tools/em/index.php:0
    2 ux_sc_mod_tools_em_index->main() /data/htdocs/typo3_src-4.1/typo3/mod/tools/em/index.php:54
    3 ux_sc_mod_tools_em_index->importextfromrep() /data/htdocs/typo3_src-4.1/typo3/mod/tools/em/class.em_index.php:534
    4 end () /data/htdocs/typo3_src-4.1/typo3/mod/tools/em/class.em_index.php:1719

ext_emconf.php:

‘constraints’ => array(
‘depends’ => array(
‘php’ => ’3.0.0-0.0.0’,
‘typo3’ => ’3.8.0-4.1.99’,
),
‘conflicts’ => array(
),
‘suggests’ => array(
‘partner’ => ‘’,
‘tt_address’ => ‘’,
‘captcha’ => ‘’,
‘date2cal’ => ‘’,
‘rlmp_dateselectlib’ => ‘’,
‘gabriel’ => ‘’,
),
),

(issue imported from #M5338)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.