extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2024-03-21T11:33:31Zhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/618Error while transferring extensions2024-03-21T11:33:31ZSimon PraetoriusError while transferring extensionsHi everyone! We are transferring a few extensions at the moment, and we're getting an error message. It seems to work just fine, so we're assuming (after checking the code) that the TER can't send the mail
![Bildschirmfoto_2024-03-21_um...Hi everyone! We are transferring a few extensions at the moment, and we're getting an error message. It seems to work just fine, so we're assuming (after checking the code) that the TER can't send the mail
![Bildschirmfoto_2024-03-21_um_11.31.21](/uploads/c58f0e9586fbe864a25d5f74b9ac22a3/Bildschirmfoto_2024-03-21_um_11.31.21.png)https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/617default documentation contains outdated link2024-02-27T09:36:08ZFranz Holzingerdefault documentation contains outdated link### Problem to solve
When the extension configuration has no entry for the documentation link, then an outdated link is still used by default.
It is hard for the extension author to discover why the new documentation is still not render...### Problem to solve
When the extension configuration has no entry for the documentation link, then an outdated link is still used by default.
It is hard for the extension author to discover why the new documentation is still not rendered in the front end.
### Further details
See discussion at
https://typo3.slack.com/archives/C028JEPJL/p1708972055594039?thread_ts=1708285863.530439&cid=C028JEPJL
After changing of the documentation into the new format, there is always the outdated documentation shown. It has turned out that the default extensions.typo3.org configuration always leads to the outdated link by default.
### Proposal
The default documentation link for an extension must be at https://docs.typo3.org/p/jambagecom/tt-board/main/en-us/ as soons as something is available there.
Or alternatively show an error message that there is a new documentation on the new link to inform the extension developer about the reason what he is still missing.
### What does success look like, and how can we measure that?
Remove the documentation link in the extension configuration.
Check that the extension will not propose the following outdated link if there is already a newly generated documentation in the new format at the new link (listed above):
https://docs.typo3.org/typo3cms/extensions/tt_board/stable/
### Links / referenceshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/616Server Migration2024-02-06T08:53:39ZAndri SteinerServer Migration* the server in use to run extensions.typo3.org is based on Debian 10, which will be EOL in July this year
* as soon as you plan a larger deployment (maybe a upcoming TYPO3 update?), please contact the server team to switch to a new server* the server in use to run extensions.typo3.org is based on Debian 10, which will be EOL in July this year
* as soon as you plan a larger deployment (maybe a upcoming TYPO3 update?), please contact the server team to switch to a new serverhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/615Number in "Downloads by month" infographic is sometimes not displayed2024-01-31T12:30:04ZEric HarrerNumber in "Downloads by month" infographic is sometimes not displayedIn some cases, the total downloads by month are not displayed. I have currently noticed this behavior on the following page, for example:
<br>https://extensions.typo3.org/extension/klaro_consent_manager
The number is not displayed afte...In some cases, the total downloads by month are not displayed. I have currently noticed this behavior on the following page, for example:
<br>https://extensions.typo3.org/extension/klaro_consent_manager
The number is not displayed after the initial loading of the page. When selecting/deselecting the filters, the number appears and is hidden again.
![Bildschirmaufnahme_2024-01-31_um_13.24.57](/uploads/4dfc6f3b6da2d96372bb4368dc1beb75/Bildschirmaufnahme_2024-01-31_um_13.24.57.mov)
When I take a look at the SVG code of the graphic, I notice that the attribute `visibility="hidden"` is set incorrectly.
```xml
<text x="601" style="font-size:11px;font-weight:bold;color:gray;fill:gray;" text-anchor="middle" transform="translate(0,0)" y="140" opacity="0" visibility="hidden"><tspan x="601" y="140" class="highcharts-text-outline" fill="#FFFFFF" stroke="#FFFFFF" stroke-width="2px" stroke-linejoin="round">71</tspan><tspan x="601" y="140">71</tspan></text>
```https://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/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/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/610Search suggestion generates wrong url2024-01-05T16:16:03ZJustus MoroniSearch suggestion generates wrong url### Summary
When using the search on extensions.typo3.org with "tailwind" a search suggestion is shown "tailwindcs".
When clicking on that link the search is reset. The url param "q" seems wrong and needs to be in the solr namespace.
...### Summary
When using the search on extensions.typo3.org with "tailwind" a search suggestion is shown "tailwindcs".
When clicking on that link the search is reset. The url param "q" seems wrong and needs to be in the solr namespace.
### Steps to reproduce
1. Go to: https://extensions.typo3.org/?L=0&id=1&tx_solr%5Bq%5D=tailwind
2. Click the "tailwindcs" link
### Example URL
https://extensions.typo3.org/?L=0&id=1&tx_solr%5Bq%5D=tailwind
### What is the current *bug* behavior?
The generated suggestion for "tailwindcs" generates the following link:
https://extensions.typo3.org/?q=tailwindcs
### What is the expected *correct* behavior?
The generated suggestion for "tailwindcs" should generate the following link:
https://extensions.typo3.org/?L=0&id=1&tx_solr%5Bq%5D=tailwindcs
**Acceptence Criterias**
* [ ] Suggestion link should work as expected
### Relevant logs and/or screenshots
![Bildschirmfoto_2024-01-05_um_17.07.16](/uploads/839a3cf3b635f6e797762842026343ec/Bildschirmfoto_2024-01-05_um_17.07.16.png)
### Possible fixes
This "additionalParams" in this line are wrong:
https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/blob/develop/extensions/ter_layout/Resources/Private/Templates/Solr/Search/Results.html?ref_type=heads#L48
```
<f:link.page additionalParams="{q:suggestion.suggestion}">{suggestion.suggestion}</f:link.page>
```
The "additionalParams" need to be like in this line:
https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/blob/develop/extensions/ter_layout/Resources/Private/Templates/Solr/Search/Results.html?ref_type=heads#L18
```
<f:link.page additionalParams="{tx_solr:{q:suggestion.suggestion}}">{suggestion.suggestion}</f:link.page>
```https://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/608Delete package from TER that is only available on packagist2024-01-03T08:37:52ZSimon SchaufelbergerDelete package from TER that is only available on packagist### Describe the task
The extension https://extensions.typo3.org/extension/typo3_phone is only available on packagist but I had to publish a placeholder extension on TER for visibility. Now that the extension can be imported, the TER ve...### Describe the task
The extension https://extensions.typo3.org/extension/typo3_phone is only available on packagist but I had to publish a placeholder extension on TER for visibility. Now that the extension can be imported, the TER version can be completely deleted as the extension can only be installed via composer because of its dependencies.
### What does success look like, and how can we measure that?
Please delete the extension in the database so that it can be imported via packagist.
**Acceptence Criterias**
* [ ] Extension is not just abandoned but completely deleted.
### Links / referenceshttps://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/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/605Clearly label extensions imported from Packagist2023-12-21T08:52:01ZEric HarrerClearly label extensions imported from PackagistTo avoid raising false expectations among inexperienced users, extensions that have not been explicitly published by the author in the TER must be clearly labeled.
For example, the following warning (similar to the "Outdated extension" ...To avoid raising false expectations among inexperienced users, extensions that have not been explicitly published by the author in the TER must be clearly labeled.
For example, the following warning (similar to the "Outdated extension" warning) would be conceivable:
"**Imported extension**
This extension has not been explicitly published in this extension repository. Be aware that the documentation, flexibility and maintenance of this extension may be of lower quality."https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/604Filtering by publishing channel2023-12-20T09:13:55ZEric HarrerFiltering by publishing channelWith the Packagist integration, there is no way to clearly distinguish in the TYPO3 Extension Repository (TER) between extensions that have been explicitly loaded into the TER and those that have been determined and imported exclusively ...With the Packagist integration, there is no way to clearly distinguish in the TYPO3 Extension Repository (TER) between extensions that have been explicitly loaded into the TER and those that have been determined and imported exclusively via the Packagist API.
The author's publishing behavior is an indicator of the quality of the documentation and the flexibility of the extension. In case of doubt, the user must read/understand more code in order to use the extension in a meaningful way. An effort that not everyone wants to make.
For this reason, we need a new "Publishing Channel" filter in the TER search with the values "Packagist" and "Extension Repository". If one only select "Packagist", then only imported extensions will be displayed.
If one selects "Extension Repository", then only those extensions are displayed that have been explicitly published in the TER, as was the case before Packagist integration.https://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/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/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/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/599Admin transfer throws error2024-03-21T11:33:32ZStefan BusemannAdmin transfer throws error
### Summary
503 Message in fe when an admin tries to transfer an ext key.
### Steps to reproduce
1. Login as admin in FE
2. transfer an ext key to another user
### What is the current *bug* behavior?
Error message in log:
> Core: ...
### Summary
503 Message in fe when an admin tries to transfer an ext key.
### Steps to reproduce
1. Login as admin in FE
2. transfer an ext key to another user
### What is the current *bug* behavior?
Error message in log:
> Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function setDefaultQuerySettings() on null | Error thrown in file /home/extensions-prod/ci/releases/62/extensions/ter_fe2/Classes/Service/ExtkeyTransferMailService.php in line 42. Requested URL: https://extensions.typo3.org/my-extensions?tx_terfe2_pi1%5Baction%5D=transfer&tx_terfe2_pi1%5Bcontroller%5D=Registerkey&cHash=658869f052e5cc19dddedbe9b3a54072
### What is the expected *correct* behavior?
Confirmation message is expected
**Acceptence Criterias**
* [ ] transfer process must work
* [ ] no error is shown in log
* [ ] fe shows a flash message about the status of the transfer
### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)Backlog