Bug #24734
closed
Inconsistent Extension List (Update Status) + minor CSS-Fixes
Added by Daniel Felix almost 14 years ago.
Updated over 10 years ago.
Description
I've just found a little missbehaviour of the new extension manager.
Ways to reproduce:
1. go to: Extensions Manager -> pulldown "Extension Manager" -> Tab "Remote Repository" -> "Retrieve/Update"
2. The current repository will be shown.
3. go to: pulldown "Extension import"
4. Last import isn't changed. You can reimport the Extension List, which cause a second time repository traffic
---------------------------------------
I've just attach some PNG's which are showing some css related issues.
Best regards,
Daniel
(issue imported from #M17224)
Files
Another Question:
Could those pulldown menu "extension update" moved to the new extension manager? maybe the "old" pulldown-items could be removed then?
I can't follow your problem description.
The images with css issues are already solved, Scrollbars are os-related, so they can't be styled.
I know, that scrollbars, are browserspecific, but the area, which is scrollable, could be defined via html/css.
Those arrow is stopping just right away in this darker grey header area.
I haven't take a second look at the backend right now, it's late. But the other issue's were present, as i opened this ticket. If those errors are resolved (in chrome too...), this ticket could be closed.
What's about those second question (extension update -> extension manager)? This could be a way to "clean up" those pulldown.
- Status changed from New to Needs Feedback
- Target version deleted (
0)
- TYPO3 Version set to 4.5
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1.7)?
Cause of the rewritten Extension Manager IMHO the parts of the given screenshots do not exists anymore in newer TYPO3 version.
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF