Bug #30671: EM: ext_update not working - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Actions

Copy link

Bug #30671

closed

EM: ext_update not working

Added by Felix Kopp about 13 years ago. Updated over 11 years ago.

Status:

Closed

Priority:

Must have

Assignee:

Category:

Target version:

Start date:

2011-10-08

Due date:

% Done:

Estimated time:

TYPO3 Version:

4.6

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

in new EM the ext_update functions are not working.
This should be an extra tab.

Example: tt_news.

History
Notes
Property changes

Actions

Copy link

Updated by Markus Klein about 13 years ago

The update link is shown on the very first tab and opens a window.

What does "not working" mean? Error message, Exception?

Actions

Copy link

Updated by Anonymous over 12 years ago

experiencing a strange behaviour with TYPO3 4.5 and the localized versions of static_info_tables, e.g. static_info_tables_de and _fr.

i see the update link in the first tab of the extensions, but the popup is empty.

as workaround i called the update script manually:
http://www.XXXX.de/typo3/mod.php?M=tools_em&nodoc=1&CMD[showExt]=static_info_tables_de&SET[singleDetails]=updateModule

Actions

Copy link

Updated by Stefan Galinski over 12 years ago

Status changed from New to Needs Feedback

Just tried it myself with the latest 4.5 trunk and static_info_tables_de, but the popup wasn't empty. In my case this was an installation inside a subdirectory. Can you try to circle the necessary environment settings that triggers the bug?

Actions

Copy link

Updated by Anonymous over 12 years ago

hm, tried to reproduce it today and the damn thing worked as expected. the only thing that changed since yesterday is the fact that the database tables of static_info_tables_de have been converted from latin1 to utf8. the typo3 was already set to utf8 yesterday. maybe that difference caused the error...

Actions

Copy link