blog.Resource
August 6, 2013

TER Extension upload

By: Thomas Löffler

extension_uploader possibilities

extension_uploader Screenshot

TER changed

Many people recognized the new conditions for uploading extensions into TER. You always have to set the dependencies to an actually supported TYPO3 version.

This is a good thing to hide extensions which will not maintained any more.

But also the upload changed...

TYPO3 >= 6.0

In TYPO3 >= 6.0 you will miss the "Upload to TER" possibility in the Extension Manager. The EM is completely rewritten and many things like the language and the TER upload part were pulled out of this extension.

You can see a new language module in the Backend, but what about uploading an extension?

The new CLI support

Honestly, I don't know who was the first. Two people are maintaining a CLI tool for e.g. uploading extensions to TER. The results of Tobias Liebig [1] and Elmar Hinz [2] can be found on GitHub.

This tool is really easy and awesome, because you get more information on what happened if an upload fails.

But you have to pay attention about the process before uploading. In EM <= 6.0 you could select the target version of your extension.

If you upload by CLI you have to set the target version of your extension in the ext_emconf.php by yourself. Otherwise you overwrite your current version.

Maybe someone can get a hand on this to improve the CLI script. But for a fast and easy solution, this is my favorite.

Extension upload within TYPO3

Months after the release of TYPO3 6.0 Georg Großberger released the extension "extension_uploader" [3] which handles the TER upload within the TYPO3 Backend.

I have not uploaded an extension with it yet, but for people with no possibility for CLI usage or lovers of the easy handling in the TYPO3 Backend it is a good alternative.

There you can not only set a bugfix, minor or major release, even a custom release number can be set!

A very cool feature would be a nice possibility to set the TYPO3 version dependency without editing the ext_emconf.php

[1] https://github.com/etobi/Typo3ExtensionUtils
[2] https://github.com/t3elmar/Typo3ExtensionUtils
[3] http://typo3.org/extensions/repository/view/extension_uploader


comments

comment #1
Gravatar: Tobias Liebig Tobias Liebig August 6, 2013 12:10
Also Christian Zenker is working on a 2.0 of the Typo3ExtensionUtils which is based on SF/Console and improves a lot regarding usability and code quality.

Give it a try and test it, too:
https://github.com/czenker/Typo3ExtensionUtils/tree/dev-2.0

comment #2
Gravatar: Jan Bartels Jan Bartels August 6, 2013 19:26
What about an upload directly from Forge to TER? It would be great if a tagged version of an extension in a SVN- or GIT-repository of Forge could be published in TER without having to use any third-party tools like the new CLI-utilities or special TER-upload-extensions.

comment #3
Gravatar: Steffen Gebert Steffen Gebert August 7, 2013 10:31
Jan, that's the thing we're dreaming of in sleepless nights. Unfortunately, some work has to be done until then.
Are you interested in supporting us with this? Besides the small problem to create a script that is triggered after tagging and calls the uploader, we have to ensure that forge project owners match the owner of extension keys. That's unfortunately still not the case :-(

Steffen

comment #4
Gravatar: Jan Bartels Jan Bartels August 7, 2013 23:27
Steffen, thanks for the clarification, but I don't think that I have the deep knowledge that is clearly neccessary to realize that task, I'm afraid. I wasn't aware of the difficulties that can arise.

If the project owners in Forge and TER don't match, the automatic upload could be stopped. It should be a matter of the extension teams to setup the ownerships in Forge and TER correctly if they want to use that feature.

Sorry, comments are closed for this post.