TYPO3 Core

Helmut Hummel wrote:

Frank Gerards wrote:

why is the "download as .t3x" function gone ?

Because we did not consider this format useful. It only made things more complicated.

Well, maybe you thought too simple then ;).

Why wasnt that announced ?

If it is not in NEWS.txt we missed to announce that, sorry

ok, it

Is .t3x support dropped in TYPO3 v6.x ?

You can still import extensions in t3x format, but export in that format is dropped.

Why do you ask? What is your usecase for the t3x format?

i.e. export a extension version (own extension) from developer instance and re-import it on live-instance, i.e. for a quick fix.

Dropping export wouldnt be a problem, BUT in older versions you CANNOT import .zip files into the EM. So in 2 cases i wrote a backwards-compatible v6.x extension and wanted to import it into 4.7.x instances (which all is the workflow if you do random freelance work without having access to the internal web dev-flow of a company), which now fails as .zip extension files cannot be imported to older TYPO3 versions.

I would consider this a BREAKING CHANGE and this should be made public as I saw in typo3 irc-chat 3 more ppl having probs with that thing.
maybe consider moving that .t3x-Export-functionality into deveval too ?

Hello Frank,

thank you for the notice.

The migration from T3X to ZIP is followed by several teams (typo3.org, core, …).
We are sorry if that is a problem for you.

The focus will be on ZIP for the future.

I close the issue at this point for now.
Sorry again

Please consider that you can download t3x files on typo3.org

as long as version 4(.7) is supported, this bug is not solved. The EM expects the file extension of manually importetd extensions to be .t3x. .zip is not accepted. This should be changed to allow direct transfer of extensions via different TYPO3-sites like Frank described. So this is rather a 4.x bug now.

As a developer, you can always copy the directory to a 4-7 instance (that you need anyway for testing) and export it from there.

But somehow "T3X" is kind of a brand like TYPO3 itself.

If you talk about a T3X in the CMS world many people know it is a TYPO3 extension like a gem is something for ruby.

The same applies to "T3D". If a TYPO3 admin comes over a ".t3d" file he knows its an export and can distinguish it from an ".t3x".

If everything is simply .zip it would be necessary to reflect the kind of package in the filename ...

I mean I don't care about the internal file format at all. If it is a .zip file or some magic mystery binary data I don't care. But the fileending should somehow reflect how such a file can get used.

It's like OpenOffice/LibreOffice who's ".sxw" or ".odt" documents are also simply ZIP files and can get decompressed if renamed.

So this issue is in fact two issues:

1. I can't download a file with the file ending I expect.
2. The file format of TYPO3 extensions has changed (before: "special" t3x format, now: zip file)

Halo guys,

can you please point out to me where I can convert .zip to .t3x? The problem is that I am having backward compatibility issue. I was developing an extension within typo3 v. 6.1 platform, which is possible for me to upload it as .zip file.

The thing is now, I have to use typo3 v. 4.5, and there are no support to upload .zip extensions. it supports only .t3x extensions.

If there are some work around that i can take to convert .zip to .t3x, that would be wonderful.. :)