TYPO3 Core

Firebug output:

JSON        
action
    "ExtDirect" 
data
    [Object {}, "20b4b5c84ed2652bfc4b540a90f4ba2b1f32e2cf"]
0
    Object {}    
1
    "20b4b5c84ed2652bfc4b540a90f4ba2b1f32e2cf" 
method
    "saveExtensionConfiguration" 
tid
    4
type
    "rpc" 
Source
{"action":"ExtDirect","method":"saveExtensionConfiguration","data":[{},"20b4b5c84ed2652bfc4b540a90f4ba2b1f32e2cf"],"type":"rpc","tid":4}

Hi Steffen,

yes it seems to be:

[Tue Dec 06 19:54:23 2011] [warn] [client HIDDEN] mod_fcgid: stderr: PHP Fatal error:  Cannot use object of type stdClass as array in /home/HIDDEN/typo3_src-4.6.1/typo3/sysext/em/classes/connection/class.tx_em_connection_extdirectserver.php on line 297, referer: http://www.HIDDEN/typo3/mod.php?M=tools_em

Trying to update any extension's settings leads to this.

Thanks much,

B.

Upgraded to 4.6.2, still the same.

Upgraded to 4.6.3, still the same.

Okay.. I found some duplicates of this issue, but all related to the Extension Manager - and I think to Ext.Direct.

Who can give me access to a test installation?

Steffen,

I can if you need.

Fine. SSH would be nice, in doubt FTP access. Please mail me to steffen.gebert@t3o. Thanks! Would be nice, if you could send me also your skype user name.

Hi Steffen,

mail sent.

Thanks :)

Okay, so who if you is using eAccelerator?

Please all check your Reports module, whether it complains about the "PHP Doc Comments" for Extbase and that you should recompile it with --with-eaccelerator-doc-comment-inclusion. The Ext.Direct API generator also uses PHP Doc "reflection" to generate the API. So this is a very good idea, which Tim Riemenschneider brought up today in the dev-List.

Boris, for you this is the case!

BTW who added Kasper as watcher? :D

I can confirm, that disabling the eaccelerator solves the problem for me. On typo 4.5.10.

Confirmed here as well, disabling eAccelerator fixes it.

Jan, which eAccelerator version were you using? I have been using eAccelerator with T3 for quite some time, and I have never seen such issue until 4.6.0 OR the version 0.9.6 OR 0.9.6.1, that's why I wasn't suspecting it as it wasn't creating such issues for me before. Just for the testing sake, I will try putting 0.9.5 branch just to see if it reproduces, and will try a couple of alternate opcode cachers like xCache or APC and see what happens with them.

Please all check your Reports module, whether it complains about the "PHP Doc Comments" for Extbase and that you should recompile it with --with-eaccelerator-doc-comment-inclusion. The Ext.Direct API generator also uses PHP Doc "reflection" to generate the API. So this is a very good idea, which Tim Riemenschneider brought up today in the dev-List.

I always had EA compiled without --with-eaccelerator-doc-comment-inclusion as I have noticed PHP segfaulting it when eAccelerator was compiled --with-eaccelerator-doc-comment-inclusion on more than one occassion, so I was always compiling it without it anyway.

Steffen, thanks a LOT :)

I'm also relieved that the root cause is finally found!

I would say that this problem would also affect you in 4.5, if you use either Extbase or the new Extension Manager.

Deactivating eaccelerator doesn´t work for me... :-( Can´t upload a extension to TER. I see only the "Please wait..." notice and this error: Fatal error: Cannot use object of type stdClass as array in /usr/www/users/vde/_sources/typo3_src-4.6.3/typo3/sysext/em/classes/connection/class.tx_em_connection_extdirectserver.php on line 657

The Ext.Direct API gets cached.. I don't know, if a new cache entry is automatically created or whether you have to clear the cache.

Could you check in Network tab of your browser's developer tool, what sent AJAX request is.

Yes I can do this, but how? I´m using FF with web developer extension.

Please install Firebug then. There's a Net tab. Have you really cleared the cache?

Maybe you could even try to delete typo3temp/(/).js to make sure that the faulty API definition is gone.

Yes I cleared the cache several times.
If I want to upload a new extension this request appears:
http://v2.domain.de/typo3/ajax.php?ajaxID=ExtDirect::route&namespace=TYPO3.EM

Date    Thu, 05 Jan 2012 08:33:24 GMT
Server    Apache
X-Powered-By    PHP/5.3.8
Expires    0
Cache-Control    no-cache, must-revalidate
Pragma    no-cache
Last-Modified    Thu, 05 Jan 2012 08:33:25 GMT
Keep-Alive    timeout=15, max=100
Connection    Keep-Alive
Transfer-Encoding    chunked
Content-Type    text/html

Host    v2.domain.de
User-Agent    Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
Accept    text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language    de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding    gzip, deflate
Accept-Charset    ISO-8859-1,utf-8;q=0.7,*;q=0.7
Connection    keep-alive
Content-Type    application/json; charset=UTF-8
X-Requested-With    XMLHttpRequest
Referer    http://v2.domain.de/typo3/mod.php?M=tools_em
Content-Length    125
Cookie    _pk_id.1.5055=d34ee0e63f270e6f.1318232454.85.1325750555.1325691405.; _pk_id.5.5055=85f468d0cd7d1c4b.1318337402.1.1318337402.1318337402.; typo3-login-cookiecheck=true; tx_phpmyadmin=f53c43c3854dea4794dad32118c9ae5c; be_typo_user=78fddb184af31fff4a87b536d7162658
Pragma    no-cache
Cache-Control    no-cache

Could you please add POST data (or content of the request - don't remember exactly)?

I hope it´s ok ;)

http://v2.domain.de/typo3/ajax.php?ajaxID=ExtDirect::route&namespace=TYPO3.EM

POST /typo3/ajax.php?ajaxID=ExtDirect::route&namespace=TYPO3.EM HTTP/1.1
Host: v2.domain.de
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Connection: keep-alive
Content-Type: application/json; charset=UTF-8
X-Requested-With: XMLHttpRequest
Referer: http://v2.domain.de/typo3/mod.php?M=tools_em
Content-Length: 124
Cookie: _pk_id.1.5055=d34ee0e63f270e6f.1318232454.85.1325750555.1325691405.; _pk_id.5.5055=85f468d0cd7d1c4b.1318337402.1.1318337402.1318337402.; typo3-login-cookiecheck=true; tx_phpmyadmin=f53c43c3854dea4794dad32118c9ae5c; be_typo_user=78fddb184af31fff4a87b536d7162658
Pragma: no-cache
Cache-Control: no-cache
{"action":"ExtDirect","method":"uploadExtToTer","data":[{},"88458d799d90537094d05197b4bc3eb077336f8f"],"type":"rpc","tid":4}

HTTP/1.1 200 OK
Date: Thu, 05 Jan 2012 08:52:27 GMT
Server: Apache
X-Powered-By: PHP/5.3.8
Expires: 0
Cache-Control: no-cache, must-revalidate
Pragma: no-cache
Last-Modified: Thu, 05 Jan 2012 08:52:28 GMT
Keep-Alive: timeout=15, max=99
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html

Okay.. again "data":[{}, .. :(

Still, it looks like eAccelerator is a good starting point. Could you post/attach a PHP info, please?

Basti, can you reproduce this in different installations on the same server / a copy of the installation on a different server?

Might be this sticks together with the problem I had (Debian Server), which occurs if you're using fast-CGI.

http://www.codeviolation.de/apache/http-request-length-exceeds-maxrequestlen/

This leads to the ext.direct error in the frontend, and an Internal Server Error 500 in the apache error log.
The following change in your apache configuration will do the trick:

We added this (mod_fcgid version 2.35):

<IfModule mod_fcgid.c>
MaxRequestLen 1000000000
</IfModule>

For mod_fcgid version 2.36, add this:

<IfModule mod_fcgid.c>
FcgidMaxRequestLen 1000000000
</IfModule> 

But why does the request length matter? Sebastian, could you check, whether without the increased limits, the data array is really empty or whether it's another bug? Problem is that in the previously mentioned cases no data is sent at all..

basti, could you please have a look at the reports module, whether the Extbase-Check for the stripped phpdoc comments fails?

Good morning,

surprise, surprise, surprise,... today the upload worked.
Maybe the reason could be the new server we´ve got last week,,,,
But the configuration ist just the same... very strange!

We just upgraded a site from 4.2.9 to 4.5.19, and ran into a problem where we needed an extension installed. We had exactly this problem:

PHP Fatal error: Cannot use object of type stdClass as array in /www/_shared/typo3_src-4.5.19/typo3/sysext/em/classes/connection/class.tx_em_connection_extdirectserver.php on line 1354

Deactivating eaccelerator helped fixing it. As we need that to run: is there a fix to this problem other than deactivation eaccelerator?

Yes, you just have to compile eAccelerator with option --with-eaccelerator-doc-comment-inclusion