Bug #16082
closed
I get a parse error when I try to upload an extension.
0%
Description
I get this when I try to upload an extension:
Parse error: parse error, unexpected T_STRING in /home/typo3_src/typo3_src-4.0/typo3/mod/tools/em/class.nusoap.php(5925) : eval()'d code on line 1
Fatal error: Cannot instantiate non-existent class: soap_proxy_959897375 in /home/typo3_src/typo3_src-4.0/typo3/mod/tools/em/class.nusoap.php(5927) : eval()'d code on line 1
In the EM I go to 'Upload to TER'.
And fill out the forms user/pass.
Changelog for upload: Initial upload.
Warning Only install this extension if you wish to grant trusted be-users access to a constant editor which traditionally is admin-only.
Upload command: New sub version (latest x.x+1.0)
Click 'upload extension'.
I don't know much about soap, so I didn't dig deep into this.
But when I debug i get the following.
in function getProxy() from line 5919:
$this->_getProxyClassCode($r) returns:"A proxy can only be created for a WSDL client". I can see that this is not the expected result.
This is what I see in function _getProxyClassCode:
$this->endpointType is empty and therefore it returns the above message.
I get this error TYPO3 4.0 final.
(issue imported from #M3327)
Files
Updated by Stig N¸rgaard over 18 years ago
PHP version is 4.3.10-16
memory_limit is 64mb
Updated by Stig N¸rgaard over 18 years ago
I might have found the cause. The server probably didn't have a connection to the internet. I'll check soon.
Updated by Stig N¸rgaard over 18 years ago
I can confirm that the problem was that the server didn't have access to the internet. My workstation was on the same local network as the server, so I had the connection to the server. But because of a misconfiguration (gateway address), the server couldn't get on the internet.
I don't know if another error message would be appropiate?
Updated by Ingmar Schlecht over 18 years ago
I just had the error on a server that was properly connected to the internet. I tried it only once and then switched to using the old 3.8.0 extension manager to upload the extension and it worked.
Updated by Karsten Dambekalns almost 18 years ago
I never got that error myself, but... after looking into the code it seems a few things come together. So I added error checking to soapclient::getProxy(). But looking at the em_soap class again it seems as if the getProxy call can be removed without any side effects, as it's return value is never used anyway and it doesn't do any internal magic.
Attached is a patch that does this and does some unrelated cleanup, too. Please test and see if everything (still) works.
Updated by Karsten Dambekalns almost 18 years ago
The patch is made against 4.x SVN but applies to 4.0.x as well.
Updated by Christian Kuhn about 13 years ago
- Status changed from New to Rejected
- Target version deleted (
0)
No further feedback for a long time and the class in question does not exist in younger TYPO3 versions anymore.