Bug #11806
closedExtension key handling requires SOAP extension
100%
Description
Don't know, if this can be changed or makes sense, but I noticed that extension key handling requires the PHP SOAP extension.
Maybe it can be degrade more graceful or just output an error, instead of an ExtDirect Exception with stack trace (and password..).
Files
Updated by Steffen Kamper over 13 years ago
- Status changed from New to Accepted
- Assignee set to Steffen Kamper
- Target version set to 4.5 beta4
i will add a check for reports module (there are already 3 integrated)
Updated by Steffen Kamper over 13 years ago
- Target version changed from 4.5 beta4 to 4.5 final
Updated by Steffen Kamper over 13 years ago
- Target version changed from 4.5 final to 4.5.1
Updated by Susanne Moog about 13 years ago
- Project changed from 1099 to TYPO3 Core
- Target version deleted (
4.5.1)
Updated by Helmut Hummel almost 13 years ago
- TYPO3 Version set to 4.5
- Complexity set to easy
Updated by Mr. Jenkins over 12 years ago
- Status changed from Accepted to Under Review
Patch set 1 of change Ifad1a7e81fbec4a22707a7a12090234dbb7b9496 has been pushed to the review server.
It is available at http://review.typo3.org/6991
Updated by Gerrit Code Review over 12 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/6991
Updated by Gerrit Code Review over 12 years ago
Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/6991
Updated by Gerrit Code Review over 12 years ago
Patch set 1 for branch TYPO3_4-6 has been pushed to the review server.
It is available at http://review.typo3.org/7333
Updated by Steffen Gebert over 12 years ago
- Assignee changed from Steffen Kamper to Steffen Gebert
Updated by Steffen Gebert over 12 years ago
- Category set to Extension Manager
- Target version set to 4.6.3
Although this error can also occur in 4.5, I would not add this check there, as soap
is not a required PHP extension in this version (was added starting with 4.6).
Extension key handling is an edge-case, I guess many developers use 4.5 to do this. Instead, adding a new requirement (at least that's how it looks like) in a patch-level release would IMHO cause more confusion. Feel free to comment, if you have a different opinion!
Updated by Mario Rimann over 12 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 1bb3587cbcd0a9fc90a40febae86c2abcf2de36c.
Updated by Xavier Perseguers over 12 years ago
- Status changed from Resolved to Closed