[TYPO3-english] 6.2 LTS - Extension manager - modified extensions

[bernd wilke]

Am 14.05.14 22:01, schrieb Ralf-Rene Schröder:
> Am 14.05.2014 17:53, schrieb Xavier Perseguers:
>> Basically it has been decided that the EM (at least the "standard" EM)
>> should not have that kind of functionality since it targets
>> administrators and not developers.
> i think it woud be VERY usefull in the "standard" EM !!!
> i.e. a company with a TYPO3 installation asked me for an update/upgrade
> (core and extensions)... i don't know the installation until now.
> For calculating the project i get a temporary admin acount to have a
> look what to do. I'm only alowed to look, not to install something. So
> it is VERY usefull to see in a "standad" feature, if it is a regular
> instalation were until now all work is correktly done and noone had
> changed extensions or core directly...
>
> If i see there are many red signs that here is somthig modified (would
> be good also for Core-Extensions), i could calculate additional work !!!

in that way: what about modifications to the core itself?
those who modify extensions in place also may modify the core files.

maybe this could be a further feature of the install-tool:
a selftest of the core if it is unmodified and complete.


for the EM I could imagine a function which calculates hashsums after an 
installation of an extension (from TER) and/or compare these hashsums to 
a list provided in the extension itself (maybe calculated in TER).
for later usage it would help a lot to see modifications to the original.
maybe the detailed information could be outsourced to an additional 
extension and EM only shows: 'has been modified'
And the additional extension could show a list of modified files  - and 
idealy show a diff to the original files which might be fetched from 
TER(?). especial after security updates it is a little bit complicated 
to get the original files for a compare of modifications.
having just the information 'has been modified' is just a start for a 
detailed analysis.


bernd
-- 
http://www.pi-phi.de/cheatsheet.html