Feature #6488

Must never stay on "Check for extensions update"

Added by Patrick Gaumond over 3 years ago. Updated over 1 year ago.

Status:Rejected Start date:2010-02-16
Priority:Should have Due date:
Assignee:Patrick Gaumond % Done:

0%
Category:-
Target version:-
TYPO3 Version:4.6 Complexity:
PHP Version:
Votes: 0

Description

Currently (4.3) if you select the menu "Check for extensions update" and then click on the Page module for example, EM remember your latest selection ("Check for extensions update") so clicking again on EM module forces EM to check again for updates. It can take a loooong time to do so.

Solution: Make "Check for extensions update" un-stockable in the session or always make EM go to "Loaded extension" first.

History

#1
Updated by Steffen Kamper over 3 years ago

As i already mentioned, my goal is to merge these views. I want to allow this check from the normal extension list, also only checking one extension for update.
I know usability of this feature atm is very bad, it's because an extension was merged with core and so there is a seperate view.

#2
Updated by Steffen Kamper over 2 years ago

  • Status changed from New to On Hold

#3
Updated by Susanne Moog almost 2 years ago

  • Project changed from Extension Manager Improvements to Core
  • Assignee set to Steffen Kamper

#4
Updated by Xavier Perseguers over 1 year ago

  • Assignee deleted (Steffen Kamper)
  • TYPO3 Version set to 4.6

#5
Updated by Stefan Neufeind over 1 year ago

Do I guess right this only applies to the separate dropdown-entry for "Check for updates" with EM1? So that's not really relevant to 4.6 anymore? Still planned to resolve as 4.5 (with EM1) is LTS?

#6
Updated by Thorsten Kahler over 1 year ago

  • Status changed from On Hold to Needs Feedback
  • Assignee set to Patrick Gaumond

I'd say this is of minor importance, because the new EM is available in TYPO3 4.5 already and it provides the possibility to filter for "updatable extensions". IMO it's up to the admin to choose the proper way (read: most appealing to him) to deal with his tasks.

Patrick, do you have any objections to closing this issue?

#7
Updated by Patrick Gaumond over 1 year ago

You can close it, we're at 4.7-DEV after all... 3 releases later.

#8
Updated by Thorsten Kahler over 1 year ago

  • Status changed from Needs Feedback to Rejected

I set it to "Rejected" because it's outdated.

Also available in: Atom PDF