Project

General

Profile

Actions

Bug #65341

closed

Extensionmanager update-button missing

Added by Gernot Ploiner over 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Category:
Extension Manager
Target version:
Start date:
2015-02-25
Due date:
% Done:

100%

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

Description

The extensionmanager in TYPO2 6.2.9 doesn't show the update button to a new version, if the installed version exist no longer in the repository.

My Example:
After an update from TYPO3 4.5 to 6.2 we want to upgrade the extension l10nmgr to the new version 3.6.3. But there is no update button.
At the moment version 3.3.4 is installed. I think we received this version directly from the developers. It is possible, that this version never showed up in TER.

If I change the Versionnumber of l10nmgr in ext_emconf to 3.3.3, which exists in TER, the update-button appears.

Solution: The update-button should always be visible, whether the older extensionversion is in TER or not.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #65117: Extensionmanager: Update of Extension with higher TYPO3-dependency not possibleClosedAlexander Opitz2015-02-17

Actions
Actions #1

Updated by Alexander Opitz over 9 years ago

  • Status changed from New to In Progress
  • Assignee set to Alexander Opitz
Actions #2

Updated by Gerrit Code Review over 9 years ago

  • Status changed from In Progress to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37236

Actions #3

Updated by Alexander Opitz over 9 years ago

HowTo test the patch with master:

As you normaly won't have an extension with a unknown version, you need to do following to test. Example for extension "news".

1.) Set the version of your example extension to a lower version then latest one, which also do not exists.

edit ext_emconf.php of news extension and set version to 3.0.99.

2.) Look into Extension manager, no updates shown for your example extension.

3.) Apply patch and look to your example extension, now you should see an update to latest version of example extension (for news it should be 3.1.0).

4.) Try updating to this version (3.1.0).

If this works all is fine.

Actions #4

Updated by Gerrit Code Review over 9 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37236

Actions #5

Updated by Gerrit Code Review over 9 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37236

Actions #6

Updated by Gerrit Code Review over 9 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37236

Actions #7

Updated by Gerrit Code Review over 9 years ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37236

Actions #8

Updated by Gerrit Code Review about 9 years ago

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37236

Actions #9

Updated by Gerrit Code Review about 9 years ago

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37236

Actions #10

Updated by Gerrit Code Review about 9 years ago

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37236

Actions #11

Updated by Gerrit Code Review about 9 years ago

Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38284

Actions #12

Updated by Alexander Opitz about 9 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #13

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF