Feature #15751
Extension Manager "Look up" shows "No matching extensions found" when "Enable unsupported extensions" is not enabled
Status: | Closed | Start date: | 2006-03-01 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Michael Stucki | % Done: | 0% |
|
Category: | Extension Manager | Spent time: | - | |
Target version: | - | |||
PHP Version: | 5 | Sprint Focus: | ||
Complexity: |
Description
When the option "Enable unsupported extensions" has not been enabled then then "Retrieve/Update" from "Import Extensions" works fine: the file typo3temp/extensions.xml.gz is created and TYPO3 shows "The extensions list has been updated and now contains 1408 extension entries".
However, when choosing "Look up" next, one might still get "No matching extensions found" until the option "Enable unsupported extensions" is activated.
Note that this is a per-user setting. So: if one admin user has set it up, then another admin user might still encounter the problem described above.
This might not be an issue for a final release. But I guess there're several options to make this more intuitive anyway:
1 do not download any unsupported extensions when this option is disabled
2 the line "The extensions list has been updated" could be enhanced to show the number of supported extensions
3 "Enable unsupported extensions" could be an option next to the "Look up" button, rather than a user setting
For now, however, I just hope others will find this comment when searching the bug database, to save some time trying to figger out what's wrong...
(issue imported from #M2742)
Related issues
Associated revisions
Fixed bug #15751: dbal does not parse setDBinit correctly (thanks to Tamer Erdogan)
git-svn-id: https://svn.typo3.org/TYPO3v4/Extensions/dbal/trunk@38342 735d13b6-9817-0410-8766-e36946ffe9aa
Backported changeset 38342 from trunk: Fixed bug #15751
git-svn-id: https://svn.typo3.org/TYPO3v4/Extensions/dbal/branches/DBAL_1-1@38343 735d13b6-9817-0410-8766-e36946ffe9aa
History
#1 Updated by Michael Stucki almost 9 years ago
I cannot reproduce this. Anyone?
#2 Updated by Karsten Dambekalns almost 9 years ago
I'd say this is solved since we show the scope that is searched (reviewed/all extensions) now above the search box.
#3 Updated by Michael Stucki almost 9 years ago
Ah, of course you are right. Thanks!