Project

General

Profile

Actions

Feature #16920

closed

Refresh left menu frame if extension with backend module was installed or removed

Added by Oliver Hader almost 18 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Extension Manager
Target version:
-
Start date:
2007-01-30
Due date:
% Done:

0%

Estimated time:
PHP Version:
5
Tags:
Complexity:
Sprint Focus:

Description

If an extension that contains a backend menu has been installed or was removed, the module link doesn't show up in the left menu frame. It's necessarry to reload manually to get the new module visible.

The extension manager could trigger an automatic reload if a module was installed or removed.

(issue imported from #M4886)


Files

0004886.patch (3.99 KB) 0004886.patch Administrator Admin, 2007-01-30 09:28
0004886_2.patch (5.45 KB) 0004886_2.patch Administrator Admin, 2007-01-30 13:40
0004886_3.patch (1.8 KB) 0004886_3.patch Administrator Admin, 2007-02-03 17:07

Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #17318: TYPO3 back-end is blocked on new installations because of a bug in RFCs #15084/#15084ClosedOliver Hader2007-05-19

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

Actions
Is duplicate of TYPO3 Core - Feature #15084: Extension Manager Feature Request: Backend Frameset does not reload when installing backend modulesClosedIngo Renner2005-10-17

Actions
Actions #1

Updated by Oliver Hader almost 18 years ago

Please have a look at the attached file 0004886.patch and test its functionality.

Actions #2

Updated by Peter Foerger almost 18 years ago

Works fine here on TYPO3 4.1beta3*PHP5*FF*OS X 10.4.8 !
What really annoys me is the logout/login procedure to awake the modules functionality. But this is another story.

Actions #3

Updated by Oliver Hader almost 18 years ago

Thanks Peter for testing the patch. I had to do some small changes to the patch. For the case, requirements of an extension didn't match the restart process lead to an endless loop.
This is fixed in 0004886_2.patch.

Actions #4

Updated by Karsten Dambekalns almost 18 years ago

~12059: You can also just reload the whole BE frameset, see also comments to #15084

Actions #5

Updated by Oliver Hader almost 18 years ago

Karsten, thanks for the hint! A link which offers to reload the whole backend and that appears only when an extension containing modules was installed, is simple and helpful. The attached new file (0004886_3.patch) implements this feature...

Actions #6

Updated by Ingo Renner over 17 years ago

the patch was partially used for fixing 584, so just little work is left here...

Actions #7

Updated by Ingo Renner over 17 years ago

fixed in SVN

Actions #8

Updated by Michael Hirdes over 17 years ago

reopened by request of Franz H.

Actions #9

Updated by Oliver Hader over 17 years ago

@Michael: Please tell us the reason for reopening this issue. What doesn't work and how can it be reproduced?

Actions #10

Updated by Ingo Renner over 17 years ago

fixed in SVN, if you have a problem with the solution, open a new report!

Actions #11

Updated by Michael Stucki over 17 years ago

@Oliver: If someone needs to explain that, then it's Franz H.

However, since he already opened bug #17318 about exactly this topic, we can close this one once again.

- michael

Actions

Also available in: Atom PDF