Bug #51820
closed
Extension Manager Problems after Upgrade from 6.0.4 to 6.1.4
Added by Andrea Böhm over 11 years ago.
Updated over 11 years ago.
Category:
Extension Manager
Description
After upgrading from 6.0.4 to 6.1.4 clicking on the "configure" button reloads the "Manage Extensions" but not the configuration options page for the respective extension.
Maybe related:
I stumbled upon this after I've noticed problems with Indexed Search. After the upgrade the search box (that is included on all pages with the same code) leads to the 404 page when the search is started from a subpage. The search works as it should when it is executed from a top level page.
In case someone encounters the same Indexed Search problem:
That was easy to solve by making the path of the form action absolut.
This of course does not help with the Extension Manager problem
I can confirm the problem with extension manager on 6.1.4. The requested url when clicking on gear icon that should open extension settings is:
http://domain.com/typo3/mod.php?M=tools_ExtensionmanagerExtensionmanager
shouldn't it leads to some controller/action and points some extension?
I have just upgraded sources to the latest git version (6.1.5-dev) through git clone and symlinked them. After clearing configuration cache / all cache i can access exension settings without any problems.
So this seems to work with 6.1.5-dev. Not sure though if it was related to sources or some cached configuration/content.
I would be nice to know which file of the source made it work again.
Andrea i don't see any change since 6.1.4 release that can have any influance on EM (see: https://github.com/TYPO3/TYPO3.CMS/commits/TYPO3_6-1) so maybe you should try to empty all typo3temp/ dir, clear configuration cache and than all cache. See if this will help on 6.1.4
- Status changed from New to Closed
- Is Regression changed from No to Yes
Hi Andrea,
this was a bug in 6.1.4, which has already been fixed in Git. The fix will be part of 6.1.5. See #51767 for more information on the fix itself.
Duplicate of #51767.
Thanks - Patch set 2 linked in #51767 solved the issue.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by