Bug #28358
New update function does not warn prominently about locally changed files
| Status: | Closed | Start date: | 2011-07-21 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | Extension Manager | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 4.6 | Is Regression: | No | |
| PHP Version: | Sprint Focus: | |||
| Complexity: | medium |
Description
The old update module marked all extensions with local changes in the update listing.
This is missing in the new EM, which just overwrites without warning.
Related issues
History
#1 Updated by Tolleiv Nietsch about 4 years ago
- Complexity set to medium
#2 Updated by Steffen Gebert about 4 years ago
- Priority changed from Must have to Should have
#3 Updated by Helmut Hummel almost 4 years ago
- Target version set to 4.6.0-RC1
#4 Updated by Xavier Perseguers almost 4 years ago
- Target version changed from 4.6.0-RC1 to 4.6.0
#5 Updated by Chris topher almost 4 years ago
- Target version changed from 4.6.0 to 4.6.1
#6 Updated by Xavier Perseguers almost 4 years ago
- Target version deleted (
4.6.1)
#7 Updated by Alexander Opitz 8 months ago
- Status changed from New to Closed
- Is Regression set to No
As this functionality is removed since 6.0 and we are moving onwards to use composer, I close this issue.
If you think that this is the wrong decision or experience this issue again, 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.
#8 Updated by Stefan Busemann 8 months ago
Yes, but using composer does not solve the issue of locally changed files.
For an administrator it should be visible in EM:- if a extension was changed locally
- warn before update to a newer version
an alternative could be #20664 - to archive older versions of extensions while updating via EM
#9 Updated by Stefan Busemann 8 months ago
So I suggest to reopen this ticket