TYPO3 Core

Ingo Renner wrote:

You don't do that on a production system.

No you probably shouldn't on a production system, I am not saying that I do, but it does not mean you even have to do it on a NON production system. The point is there is no choice to just import and not install.
And that is a security issue in my mind regardless if it is on a production system or not.

Because your non-production system is also connected to the net or how else did you get the extension in the extension manager??? That does not make it safe from a potentially malicious extension that automatically installs.

And your reply doesnt address the other issue I pointed out, sometimes you want to just import but not install an extension for modification reasons.

IMHO your rejection of this idea is not fully baked.

Also a running system is not just a production system, it is a Typo3 install in production or in a state of development/staging.

Made a related UX issue for extra feedback: Feature #50582

We need another action in between that shows all changes to be done (just as in the old (old) EM)

Philipp Gampe wrote:

We need another action in between that shows all changes to be done (just as in the old (old) EM)

I think I mentioned this in the UX issue, I agree. I thought though you could keep the current behaviour in the new EM (simple mode: auto install at own risk no questions asked.) and then a more verbose version (advanced mode:where all install/import questions are asked and options considered) and the process is thoroughly reviewed before executing.

I did find the old process in the old EM a bit clunky (@see off-topic) even though you could cope with it, it was not very clear when dealing with dependencies in what step of your initial extension install you were in when dependencies installations were being satisfied. I could imagine some nice ajax wizardy here.

Though I think the UX team might come up with a more elegant solution.

off-topic:
Another gripe of mine is that extensions installs are not very easily rolled back to previous versions. They are always overwritten, I think that is a shame. It would be cool if you could import multiple versions of the same extension, and then just symbolically link to the actively installed one. Maybe also support for an ext_rollback.php to rollback any DB/structure changes. But that would require some serious rethink of how extensions are treated.

Versioned extensions directory structure for rollback:

my_extension -> .my_extension/1.0.2
.my_extension/
  1.0.1/
  1.0.2/
  1.0.3/

It would also support old extensions that cannot be rolled back.

Anyway sorry for the Off-topic. Maybe I should post that as a far future feature or maybe it should hang in the shadows for now, I am not sure. It would be cool though.

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/30972

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/30972

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/30972

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/30972

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/30972

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/30972