Bug #64436
closed
EM isn´t showing modified extensions
0%
Description
The new EM from Typo3 6.2 doesn´t show much needed information for us system admins. When a security announcement for an extension is released, I have to check which domains (out of several hundred) use that specific extension and wether is has been modified. If it has been modified, it cannot simply be updated as this might break the website or remove important things that have been added manually before.
This has been very easy in the EM from 4.5, but there seems to be no way of getting this vital information with 6.2.
Several other users want that feature too, see discussion in:
http://forum.typo3.org/index.php/t/203799/
http://forum.typo3.org/index.php/t/200310/
Workaround:
"Check if extension has been modified" is available via https://github.com/xperseguers/t3ext-em_developer but should really be in the core installation like it used to!
Updated by Mathias Schreiber almost 10 years ago
- Target version set to 7.3 (Packages)
Updated by
Updated by Benni Mack over 9 years ago
- Target version changed from 7.3 (Packages) to 7.4 (Backend)
Updated by Nicole Cordes over 9 years ago
- Status changed from New to Needs Feedback
You can simply install the extension devtools to get a visible icon for changed extensions.
Updated by Larsen no-lastname-given over 9 years ago
I tested this with the phpMyAdmin extension that is installed globally:
- Copied "ext_tables.php" to "ext_tables.php_backup"
- Modifed "ext_tables.php" by adding two empty lines in the middle
- Installed devtools extension
I was then presented with an exclamation mark icon for phpMyAdmin. Though, when I clicked on it, the popup only showed that "ext_tables.php_backup" was added, but not that ""ext_tables.php" had been modified. Therefore, this is no help at the moment.
Also, this really should be core functionality like it used to be.
Updated by Riccardo De Contardi over 9 years ago
- Status changed from Needs Feedback to Closed
I close this as it is a duplicate of #63898 ,please continue the discussion there.
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.