extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2024-03-25T20:17:19Zhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/356Extension edit with a username with capital chars is not possible2024-03-25T20:17:19ZThomas LöfflerExtension edit with a username with capital chars is not possible## What was the cause of the issue?
With an username (stored in extensions table) with capital chars it's not possible to edit the extension data like e.g. issue tracker URL.
## Steps to reproduce
1. Change username in TER to minimum ...## What was the cause of the issue?
With an username (stored in extensions table) with capital chars it's not possible to edit the extension data like e.g. issue tracker URL.
## Steps to reproduce
1. Change username in TER to minimum one capital char
1. Try to edit your extension
## Output of error log
`You can't edit this extension because you not own it`
## Add some screenshotsBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/123My Feedback after the first look at the new TER2024-03-25T20:04:57ZXavier PerseguersMy Feedback after the first look at the new TER## Search
* [x] It should work with partial extension name, tried this: https://extensions-stage.typo3.org/?q=autoresize (no results), only works with https://extensions-stage.typo3.org/?q=image_autoresize
* [x] Message "Searched for XX...## Search
* [x] It should work with partial extension name, tried this: https://extensions-stage.typo3.org/?q=autoresize (no results), only works with https://extensions-stage.typo3.org/?q=image_autoresize
* [x] Message "Searched for XXXX. Found 5 results in 17 milliseconds" may be put into some box or made smaller, with some padding/margin
* [ ] Don't know how "facet" is intended to be used but I guess it will still come afterwards. Would be cool to be able to trim down any search by e.g., removing outdated or non-stable extensions in a result set where we basically "have what we look for, but get a bit too many names".
## Design
* [x] Would suggest to make any white text on red/green (such as version number active or download button) using bold, the contrast is otherwise not very good since the font is extremely thin
* [ ] What about adding a (big) version of ext_icon.png in the result list? This could encourage people to use a larger icon than the original 20x16 or so, since it properly resizes down anyway in TYPO3 install since many versions.
## Details
Take https://extensions-stage.typo3.org/extension/image-autoresize/
* [ ] Would love to get auto-link in the last upload comment, when it points to some "known" website, here the changelog on forge (or github, ...).
* [ ] Do you have a way to show social networks (say twitter) for the author? Often a good way to contact him/her because the doc is either missing or not well enough
* [x] orange link on blue background is not really nice visually
* [x] Installation instructions: nice! in the longer run, would be cool to get installation with packagist (composer) as well, may possibly require additional information since packagist should be privileged over our own "auto-composer-from-TER"Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/609Document packagist import2024-02-16T12:12:14ZTorben HansenDocument packagist import- Document the requirements (package type, core dependency, extension key) for packagist import on extensions.typo3.org- Document the requirements (package type, core dependency, extension key) for packagist import on extensions.typo3.orgThomas LöfflerTorben HansenThomas Löfflerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/613Prevent empty autoload information in ext_emconf.php2024-02-02T10:47:55ZTorben HansenPrevent empty autoload information in ext_emconf.phpThis commit #600 causes problems, when an extension has autoload information defined in `composer.json` but not in `ext_emconf.php`. TER should therefore not add an empty autoload information to `ext_emconf.php`, if no autoload informati...This commit #600 causes problems, when an extension has autoload information defined in `composer.json` but not in `ext_emconf.php`. TER should therefore not add an empty autoload information to `ext_emconf.php`, if no autoload information was originally provided.Torben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/601Define option to prevent package import2024-01-31T14:50:38ZTorben HansenDefine option to prevent package importIf a package author wants to prevent the import of a `typo3-cms-extension` package from packagist.org, it should be defined somewhere (e.g. `extra` section in composer.json). If the option is defined, the package should not be imported. ...If a package author wants to prevent the import of a `typo3-cms-extension` package from packagist.org, it should be defined somewhere (e.g. `extra` section in composer.json). If the option is defined, the package should not be imported. Also, an existing package should be removed, if the option is set in composer.json after the package has been imported to TER.Torben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/602Do not import composer packages with reserved extension keys2024-01-31T14:50:38ZTorben HansenDo not import composer packages with reserved extension keysIf an extension author reserved an extension key but did not upload any extension yet, the packagist package import must not import a package which uses the reserved extension key.If an extension author reserved an extension key but did not upload any extension yet, the packagist package import must not import a package which uses the reserved extension key.Torben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/603Remove possibly imported packages, if extension with same package name is upl...2024-01-31T14:50:37ZTorben HansenRemove possibly imported packages, if extension with same package name is uploadedIf an extension author uploads an extension, which has configured a known package name, a possible imported package with the same name from packagist should be removed in order to prevent duplicates.If an extension author uploads an extension, which has configured a known package name, a possible imported package with the same name from packagist should be removed in order to prevent duplicates.Torben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/606Packages that were removed from Packagist are not deleted2024-01-31T14:50:37ZChris MüllerPackages that were removed from Packagist are not deleted### Summary
Extensions deleted from Packagist are not removed from TER. Such a package has no value to users, therefore it should be deleted on TER.
### Steps to reproduce
1. Add a package to Packagist
2. Let is sync to TER
3. Remove ...### Summary
Extensions deleted from Packagist are not removed from TER. Such a package has no value to users, therefore it should be deleted on TER.
### Steps to reproduce
1. Add a package to Packagist
2. Let is sync to TER
3. Remove the package from Packagist
4. Wait for the next sync
5. It will not be removed from TER
### Example URLs
- https://extensions.typo3.org/package/brotkrueml/schema-records
- https://packagist.org/search/?query=brotkrueml%2Fschema-records
### What is the current *bug* behavior?
It stays on TER but has no value anymore for users.
### What is the expected *correct* behavior?
The extension is removed when it is not available anymore on Packagist.Torben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/607Packages that were abandoned on Packagist are not deleted2024-01-31T14:50:37ZChris MüllerPackages that were abandoned on Packagist are not deleted### Summary
Packages that were abandoned on Packagist are not deleted on TER. Such a package has no value anymore for users, so it should be removed.
### Steps to reproduce
1. Add a package to Packagist
2. Let is sync into TER
3. Aban...### Summary
Packages that were abandoned on Packagist are not deleted on TER. Such a package has no value anymore for users, so it should be removed.
### Steps to reproduce
1. Add a package to Packagist
2. Let is sync into TER
3. Abandon the package on Packagist
4. Wait for the next sync
5. The package is still on TER.
### Example URLs
- https://extensions.typo3.org/package/brotkrueml/typo3-feed-generator-mrss
- https://packagist.org/packages/brotkrueml/typo3-feed-generator-mrss
### What is the current *bug* behavior?
Abandoned packages are not removed from TER.
### What is the expected *correct* behavior?
Abandoned packages are removed from TER upon next sync.Torben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/614getNewestVersionForDependencyCheck returns wrong version2024-01-31T14:50:36ZTorben HansengetNewestVersionForDependencyCheck returns wrong version`getNewestVersionForDependencyCheck` returns the wrong version, since TYPO3 v13.0 has been released today and the function now returns 14.99.99 als latest version for dependency check, which is wrong`getNewestVersionForDependencyCheck` returns the wrong version, since TYPO3 v13.0 has been released today and the function now returns 14.99.99 als latest version for dependency check, which is wrongTorben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/600Autoload Information missing in EMCONF Array2024-01-30T13:12:50ZTim WeisenbergerAutoload Information missing in EMCONF Array### Summary
When a new version of an extension is uploaded to the TER, the ZIP file is converted to an T3X. While extracting the EMCONF array from the files the information about autoloading is ignored.
(see https://forge.typo3.org/iss...### Summary
When a new version of an extension is uploaded to the TER, the ZIP file is converted to an T3X. While extracting the EMCONF array from the files the information about autoloading is ignored.
(see https://forge.typo3.org/issues/102443)
### Steps to reproduce
1. Download the Extension via following URL, which is used by the TYPO3 Core Extension Manager: https://extensions.typo3.org/extension/download/autotranslate/0.9.2/t3x
2. Extract the T3X file and look for the serialized EMCONF array
### Example URL
https://extensions.typo3.org/extension/download/autotranslate/0.9.2/t3x
### What is the current *bug* behavior?
The serialized EMCONF array which is used by the extension manager in the TYPO3 Core to generate the patched ext_emconf.php file.
### What is the expected *correct* behavior?
The serialized EMCONF array should contain the autoload configuration.
**Acceptence Criterias**
* [ ] The serialized EMCONF array should contain the autoload configuration.
### Relevant logs and/or screenshots
-----
### Possible fixes
----https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/612Remove duplicated imports by packagist import2024-01-30T13:01:27ZTorben HansenRemove duplicated imports by packagist importCreate a cleanup task, so extensions which are uploaded to TER always have priority over packagist imported extensions. Packages, which might have been imported "wrong" (e.g. packagename to TER upload has been added after packagist publi...Create a cleanup task, so extensions which are uploaded to TER always have priority over packagist imported extensions. Packages, which might have been imported "wrong" (e.g. packagename to TER upload has been added after packagist publishing), should be removed by the cleanup task.
* https://extensions.typo3.org/extension/picturecredits vs. https://extensions.typo3.org/package/mfc/picturecreditsTorben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/611Link to Crowdin translations for all extensions broken2024-01-11T14:28:46ZPeter KraumeLink to Crowdin translations for all extensions broken### Summary
The link "Crowdin translations" for each extension is broken because the /invite suffix is wrong.
Apparently the Crowdin website has changed and removed the invite button.
### Steps to reproduce
Go to any extension detail ...### Summary
The link "Crowdin translations" for each extension is broken because the /invite suffix is wrong.
Apparently the Crowdin website has changed and removed the invite button.
### Steps to reproduce
Go to any extension detail page with Crowdin link and click on the "Crowdin translations" button.
### Example URL
https://extensions.typo3.org/extension/news/
### What is the current *bug* behavior?
Error page of Crowdin is displayed.
### What is the expected *correct* behavior?
You see the correct TYPO3 extension within Crowdin.Peter KraumePeter Kraumehttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/544Add option for extensions to be composer-only2023-11-23T10:56:21ZThomas LöfflerAdd option for extensions to be composer-only## Background
Some extensions may use external packages installed via composer and don't want to include those libraries into the extension as phar or as complete directories.
## Acceptance criterias
* [ ] Option to mark extension as ...## Background
Some extensions may use external packages installed via composer and don't want to include those libraries into the extension as phar or as complete directories.
## Acceptance criterias
* [ ] Option to mark extension as "composer only"
* [ ] Remove option to download as ZIP
* [ ] Replace download button in list with alternative
* [ ] Marked extensions are not listed at the Extension Manager
* [ ] Ensure that author can only add own (or allowed - how?) packages
* [ ] Ensure uniqueness of package name (deny package, if we have an extension record with same package name)
* [ ] Use packagist API to fetch package details_Ready for sprintTorben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/598Feature request: New Sorting criterium 'First uploaded'2023-11-15T20:03:25ZbeyringFeature request: New Sorting criterium 'First uploaded'### Problem to solve
At the moment I can't easily scan the list for new extensions. Or at least I don't know of such a function.
### Further details
Once a month I want to check for new extensions that might be interesting for my proj...### Problem to solve
At the moment I can't easily scan the list for new extensions. Or at least I don't know of such a function.
### Further details
Once a month I want to check for new extensions that might be interesting for my projects.
### Proposal
Add a new sorting criterium: Sort by 'First Upload'
### What does success look like, and how can we measure that?
Success is reached, when I can get a list of the latest added extensions in an easy way (Lets say up to 3 clicks?) using the UI.
**Acceptence Criterias**
see above
### Links / referencesBacklogJonas GötzeJonas Götzehttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/593PHP Warning when editing extension in backend2023-10-15T19:28:11ZTorben HansenPHP Warning when editing extension in backend`Core: Error handler (BE): PHP Warning: Undefined array key "lts" in /var/www/html/extensions/ter_fe2/Classes/Tca/FetchVerifiedVersions.php line 14``Core: Error handler (BE): PHP Warning: Undefined array key "lts" in /var/www/html/extensions/ter_fe2/Classes/Tca/FetchVerifiedVersions.php line 14`Torben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/115My Feedback after the first look at the new TER2023-10-15T19:24:17ZPeter KraumeMy Feedback after the first look at the new TERHere is my feedback after the first look at the new TER.
I was not involved in the plannings and ideas so far, so please take everything as a suggestion and not as criticism. And I won't be offended if you decline my suggestions!
I tried...Here is my feedback after the first look at the new TER.
I was not involved in the plannings and ideas so far, so please take everything as a suggestion and not as criticism. And I won't be offended if you decline my suggestions!
I tried to view the TER with the eyes of someone new to TYPO3 or not that familiar with the background of the TER.
- List View
- make search field always visible. Searching for extensions is the key feature of the TER and thus should be accessible easily.
- condense the list view. I've a huge screen but see only 2 extensions in list view.
- Detail View
- Installation: add a 3rd tab: install via composer and add package name from composer.json. Fallback could be typo3-ter/extkey.
- Version history: better distribution of columns. "Upload comment" should get much more space to have a more condensed view on that table.
- Version history: the "i" icon before the "Version" column name tricked me to try whether there is a tooltip.
- insecure extension versions: please add some kind of hint why there is no download button and the row is highlighted in red
- RealURL Configuration for tx_terfe2_pi would be awesomeSeptember 2023Stefan BusemannStefan Busemannhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/579Add possibility to lock extension upload2023-10-15T19:24:07ZTorben HansenAdd possibility to lock extension upload### Problem to solve
Prevent upload of new extension versions, if all extension versions are marked as insecure.
### Further details
In case all versions of a TYPO3 extension has been marked as insecure, because the extension author d...### Problem to solve
Prevent upload of new extension versions, if all extension versions are marked as insecure.
### Further details
In case all versions of a TYPO3 extension has been marked as insecure, because the extension author did not reply on email from the TYPO3 Security Team, it should be possible to manually define a "upload lock" for an extension. For extensions flagged with the "upload lock", the extension author can not upload a new version of the extension. Instead, a message is shown, that the extension author must contact the TYPO3 security team.
It must be ensured, that the upload using the UI as well as the upload using the TER REST api is prevented for extensions which have been marked with the new property "upload lock".
### Links / referencesTorben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/595Avoid ObjectManager usage in ext:ter_fe22023-10-15T19:22:40ZTorben HansenAvoid ObjectManager usage in ext:ter_fe2Extbase `ObjectManager` is deprecated since TYPO3 11.5 and removed in TYPO3 12.4. All `ObjectManager` usages can either be replaced by `GeneralUtility::makeInstance()` or by Dependency Injection.Extbase `ObjectManager` is deprecated since TYPO3 11.5 and removed in TYPO3 12.4. All `ObjectManager` usages can either be replaced by `GeneralUtility::makeInstance()` or by Dependency Injection.Torben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/591Install instructions for Distributions2023-08-15T19:55:33ZgilbertsoftInstall instructions for Distributions### Describe the task
For distributions it's essential to run `typo3 extension:setup` after require the package with Composer.
### Further details
This instruction could be added for extensions of type distrubtion after the composer ...### Describe the task
For distributions it's essential to run `typo3 extension:setup` after require the package with Composer.
### Further details
This instruction could be added for extensions of type distrubtion after the composer require command.
![grafik](/uploads/85afe8858ffffec73065402b08ddecae/grafik.png)
### What does success look like, and how can we measure that?
<!--- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this -->
**Acceptence Criterias**
* [ ] `typo3 extension:setup` is mentioned
### Links / references
https://github.com/FriendsOfTYPO3/introduction/issues/105gilbertsoftgilbertsoft