Project

General

Profile

Actions

Bug #57200

closed

Update-Icon not shown for manually uploaded extensions

Added by Jost Baron about 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Extension Manager
Target version:
-
Start date:
2014-03-23
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

After uploading an extension manually, the extension manager does not show the option to update it, even if there is a newer version available in TER, and that version is compatible to the current environment. This happens on current master (2144d4c6e0f997f824e9dc41eb3eafb2b48a180d).

Steps to reproduce:

1. Install TYPO3 with current master
2. Download EXT:news in an older version: https://typo3.org/extensions/repository/download/news/2.2.1/t3x/ and install it using the upload form in the extension manager
3. Update the Extension list from TER, if not already done
4. The update icon is not there for EXT:news. It does not matter if the extension list is updated again or not.

This could be security-related, since hides available extension updates. This gets even more problematic with the release of 6.2, since many extensions are not officially compatible, but work with it. To install them, the manual upload functionality of the extension manager is the most easy way.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #53576: Hide update icon if extension isn't compatibleClosedNicole Cordes2013-11-12

Actions
Actions #1

Updated by Jost Baron about 10 years ago

Same thing happens when the extension is manually extracted into typo3conf/ext. Clearing all caches (in the install tool) does not help.

Actions #2

Updated by Georg Ringer about 10 years ago

  • Subject changed from [Security?] Update-Icon not shown for manually uploaded extensions to Update-Icon not shown for manually uploaded extensions
Actions #3

Updated by Georg Ringer about 10 years ago

i see no security related problem there.

Actions #4

Updated by Philipp Gampe about 10 years ago

  • Status changed from New to Needs Feedback

Can you verify this behavior with RC2?

Actions #5

Updated by Philipp Gampe about 10 years ago

Most likely a dependency is not fulfilled, e.g. the max TYPO3 version allowed is lower that the current version or the PHP version allowed is lower than the current.

Please have a look at #53576.

Actions #6

Updated by Philipp Gampe about 10 years ago

IMHO we should still show the update icon, but make it grey and let it show the dependencies that are required for an update on hover.

Actions #7

Updated by Susanne Moog almost 10 years ago

I would not show an action icon for an action that is not available, on an older installation you'd then get icons everywhere with which you can't do anything. Normally the missing dependency for the update of an extension will be the TYPO3 version (especially in case you use git master ;)) - but an available TYPO3 update should not be communicated via the extensions.

Actions #8

Updated by Jost Baron almost 10 years ago

I don't think it is good to remove the info about available extension updates alltogether. The problem is that some people (me included) look for available updates in the extension manager, and if there is no indication of an available update, they tend to think that no update is available.

I think that showing the icons, but grayed out would be a good solution, since it a) shows that updates are available, and b) bugs the user to update their TYPO3. Additionally, a title tag (or some other, more obvious ui-element) with more detailed info about the missing dependencies would be nice. This helps the integrator to make an informed decision (instead to making the decision for him, as it is now).

Actions #9

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to New
Actions #10

Updated by Mathias Schreiber over 9 years ago

  • Status changed from New to Closed

Taken into account in #63909.
The issues are not linked on purpose, so the refactoring ticket does not get bloated with relations.

Actions

Also available in: Atom PDF