Feature #20664

When updating an extension, archive the old version

Added by Ingo Renner over 12 years ago. Updated about 7 years ago.

Could have
Extension Manager
Target version:
Start date:
Due date:
% Done:


Estimated time:
PHP Version:
Sprint Focus:


Currently when updating an extension, the extension is overwritten.

Now it would be nice to have the old extension archived into a different directory (f.e. typo3conf/ext_archive)


  • making it possible to easily jump back to the old version if something is not working anymore
  • easily jump back if the admin didn't notice that the extension was changed and now stuff is not working anymore
  • in an update script it would be possible to determine which version of an extension was installed before and which actions need to be executed to update data and the like with minimal effort

(issue imported from #M11402)

Related issues

Related to TYPO3 Core - Bug #28358: New update function does not warn prominently about locally changed filesClosed2011-07-21


Updated by Steffen Kamper over 12 years ago

is this needed? You can switch back to any version if something goes wrong


Updated by Ingo Renner over 12 years ago

see my points, those are not the regular "go back to a previous version" scenarios ;)


Updated by Björn Pedersen over 10 years ago

  • Target version deleted (0)

A backup option is warranted if there are local changes in an extension.


Updated by Helmut Hummel over 10 years ago

  • Priority changed from Should have to Could have

Updated by Mathias Schreiber about 7 years ago

  • Status changed from New to Needs Feedback

Hey Ingo, would you still consider this today?

Otherwise I'd close down the issue


Updated by Ingo Renner about 7 years ago

I'd argue that people should use proper versioning tools, but OTOH there might still be scenarios were it might be helpful to allow a quick rewind.

Apart from that, the last point is still valid, knowing what version was the last would allow better automated upgrade scripts.


Updated by Alexander Opitz about 7 years ago

  • Status changed from Needs Feedback to New

Updated by Mathias Schreiber about 7 years ago

  • Status changed from New to Closed

Taken into account in #63909.
The issues are not linked on purpose, so the refactoring ticket does not get bloated with relations.

Also available in: Atom PDF