Bug #38906
closed
Extension Manager doesn't show ANY Available Extensions
Added by Phil over 12 years ago. Updated over 9 years ago.
0%
Description
The backend extension manager doesn't show any installed or other extensions under "available extensions".
Files
| typo3_bug.PNG (61.2 KB) typo3_bug.PNG | Phil , 2012-07-12 15:53 | ||
| class.typo3ajax.php.patch (2.08 KB) class.typo3ajax.php.patch | Workaround | Anonymous, 2012-07-13 11:38 |
Updated by Anonymous over 12 years ago
We have upgraded to PHP version 5.3.14 and have the same problem. I read in the [TYPO3-german] mailinglist there was a discussion that it could be caused by the different behaviour of json_encode(). See http://lists.typo3.org/pipermail/typo3-german/2012-June/086261.html and https://bugs.php.net/bug.php?id=61537
Michael
Updated by Markus Klein over 12 years ago
What happens if you clear all filters? (Button in your screenshot)
Updated by Phil over 12 years ago
Michael Telgkamp wrote:
We have upgraded to PHP version 5.3.14 and have the same problem. I read in the [TYPO3-german] mailinglist there was a discussion that it could be caused by the different behaviour of json_encode(). See http://lists.typo3.org/pipermail/typo3-german/2012-June/086261.html and https://bugs.php.net/bug.php?id=61537
Michael
We have
Apache/2.2.16 (Debian)PHP-Version:5.3.14-1~dotdeb.0
and a new setup up of typo3 4.7.2 works on the server - it happens only when I update a 4.6.x to a 4.7.x version
And yes - I did a version update ;)
The new empty setup and the updatet version share the same source via symlink.
Guess there must be something going wrong during the update...
Updated by Phil over 12 years ago
Markus Klein wrote:
What happens if you clear all filters? (Button in your screenshot)
I can clear the filter or choose any possible option - nothing changes - still empty.
Updated by Phil over 12 years ago
I don't know if this has something to do with that bug, every time I call the extension manager I'll gett this logged:Core: Error handler (BE): PHP Warning: json_encode(): Invalid UTF-8 sequence in argument in /var/lib/typo3/typo3_src-4.7.2/typo3/classes/class.typo3ajax.php line 275
Updated by Anonymous over 12 years ago
For me the workaround of the German mailinglist works fine, so it is definetly something in the data passed to json_encode function. Maybe $this->content needs to be cleaned before json_encode is called? I have not yet figured out the invalid UTF-8 sequence inside $this->content.
I attached the workaround of the mailing list to use __json_encode function if json_encode of the new php version does not work due to an invalid UTF-8 sequence.
We use:
PHP 5.3.14-1~dotdeb.0 with Suhosin-Patch
Typo3 4.6.10
Updated by Phil over 12 years ago
I installed a new site on the same server. Source symlinked with the same source code as the site there the error occured. Transfered the database by sql - and everything is fine now.
So it can't be something with php - same server, same version. Same plugins - I don't know why it works now. But it is reproducable...
Updated by Grothe over 12 years ago
The charset of a file ext_emconf.php was not UTF-8. If there are special characters, then it comes to this error.
I converted the file and the problem was solved.
Updated by Anonymous over 12 years ago
Confirmed, also for me it was one ext_emconf.php file that was not utf8 encoded and thus broke the json_encode(). Maybe there is a possibilty to show an explaining error message if this occurs?
With the utf8 encoded ext_emconf.php everything works fine for me again.
Updated by Wouter Wolters almost 10 years ago
- Status changed from New to Needs Feedback
- Is Regression set to No
Hi,
does the problem still exists within newer versions of TYPO3 CMS (6.2.9)?
Updated by Christian Kuhn over 9 years ago
- Status changed from Needs Feedback to Closed
Hey. I'm closing this issue: It will no longer be fixed in 4.5 and does not happen in 6.2.