Project

General

Profile

Actions

Bug #58016

closed

module list is not refreshed after installing new extensions

Added by Kay Strobach about 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extension Manager
Target version:
-
Start date:
2014-04-17
Due date:
% Done:

0%

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

Description

releases: 6.0, 6.1, 6.2

after installing an extension with the 6.x extensionmanger the backend module list in the left is not refreshed.
this was a nice feature in 4.x ...

I think there is just a bit of JS missing


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #64733: extension list is not updated after an extension is updatedClosed2015-02-02

Actions
Related to TYPO3 Core - Bug #64079: Extension manager doesn't emit "hasInstalledExtensions" signal after extension uploadClosed2015-01-02

Actions
Is duplicate of TYPO3 Core - Bug #42009: Enable extenisions with BE modules don't refresh the module listClosedOliver Hader2012-10-15

Actions
Actions #1

Updated by Oliver Hader almost 10 years ago

Hm, I already fixed that for 6.0 with issue #42009 - seems like it got removed again...

Actions #2

Updated by Oliver Hader almost 10 years ago

  • Status changed from New to Needs Feedback
  • Is Regression changed from Yes to No

Cannot reproduce with TYPO3 CMS 6.2.
Can you please provide a screenshot to ensure that we're talking about the same?
I e.g. installed and uninstalled the documentation module which perfectly appeared and disappeared in the module menu on the very left side of the TYPO3 backend.

Actions #3

Updated by Kay Strobach almost 10 years ago

works if you download from TER
but not if you upload from your PC

Actions #4

Updated by Alexander Opitz over 9 years ago

Hi,

was this issue fixed with TYPO3 6.2.4 or does it still exists?

Actions #5

Updated by Kay Strobach over 9 years ago

sometimes that behaviour is still there, but not always, one case is if you change the settings and "enable / disable" a module, but that's not the typical case ... happens during pure installation as well ..

Actions #6

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to New
Actions #7

Updated by Riccardo De Contardi over 8 years ago

  • Status changed from New to Closed

I close this as a duplicate of #64079, please continue the discussion there; I added a relation to #64079 to keep track of this issue.

If you think that this is the wrong decision, 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.

Actions

Also available in: Atom PDF