TYPO3 Core

Hi Jigal
how can you say that the extension filename MUST have format format <extensionKey>_<version>.zip ??

this is a new thing since 6.0, right? i don't remember to have read anything about this (quite big changing) new behavior
because em has always accepted any kind of filenames.. and it has been useful for backup purpose, to name locale, dev and prod exts etc)

the extension name is, and has always been, its folder name.

if i unzip "extname_1.0.3.zip" and "extname_1.0.3 (1).zip" , what i get is and should always be a folder named "extname"

am i wrong?

EM supports two file types for upload:
- zip; format: <extensionKey>_<version>.zip
- t3x; file name irrelevant, information about extension key is included inside file

You can download either format from the extension manager. From TER all extensions are in t3x format available, some/most are also in zip files available.

ahhh

i understood that .t3x was to be abandoned, and since 6.0 the standard format is .zip, which is far better for everybody
since this, i have been dealing with .zip only

i guess we should not support both formats forever. but for sure the .zip filename format should be more open.. at least:

<extensionKey>_<version>_<whatever-i-want>.zip

what do you think?

PS: anyway from EM i can only download .zip format.. this is why i got the problem!

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20875

Please test this change.

Patch set 3 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20875

Patch set 4 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20875

Patch set 1 for branch TYPO3_6-1 has been pushed to the review server.
It is available at https://review.typo3.org/21077

Patch set 1 for branch TYPO3_6-0 has been pushed to the review server.
It is available at https://review.typo3.org/21078

Hmm, what does "resolved" mean in this context? It is still not possible to rename / add anything behind the zipfiles version number as importing this extension will result in a wrong extension key.

In addition, using the download-button in extension manager should relly again create a filename containing a timestamp (as old extension manager used to do: extkey_version_yyddmm or similar).

@Jan Schröder you can add anything you want after the version number and it will be ignored. Only the part before the version number is used for the extension key. Take a look at the unit test.

Regarding the timestamp in the download file, please create a new issue for this. This is really easy to implement.