Bug #25390
closed
Filtering extensions on remote repository does not respect repository selection
100%
Description
I have setup an own TER and added it to the Extension Manager.
When searching for an extension in the remote repository with the "filter" text field, the currently selected repository is not taken into account and results from the main typo3 repository are returned.
Steps to reproduce, see the attached screenshot with the 4 steps:
0. A custom TER needs to be registered
1. Log into typo3 backend, extension manager. Click "remote repository".
2. The custom TER is already preselected in the dropdown
3. Type something in the filter text field and press return. Although the custom TER is selected, results from the public typo3 TER are shown
4. Open the repository dropdown and click on the already selected custom TER. The dropdown closes and the search results are reloaded, this time with the results from the custom TER.
Pressing return on the filter text field should transmit the currently selected repository.
(issue imported from #M18031)
Files
Updated by Steffen Kamper over 13 years ago
- Assignee set to Steffen Kamper
- Target version deleted (
0)
Updated by Steffen Kamper over 13 years ago
- File 25390.patch 25390.patch added
- % Done changed from 0 to 100
fix is a nobrainer, main repository was still hardcoded.
Updated by Steffen Kamper over 13 years ago
- Status changed from New to Resolved
- Target version set to 4.5.3
submitted to master and 4-5
Updated by Christian Weiske over 13 years ago
That patch does not make it any better. The originally selected repository is always used now, not the currently selected one.
In effect, I always search my own repository but not the typo3 one anymore - except when directly changing the dropdown, but text searches afterwards go to my own repo.
Updated by Oliver Hader over 13 years ago
- Status changed from Resolved to Closed
Updated by Christian Weiske over 13 years ago
Oliver, why did you close it? I don't think it works.