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/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/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/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/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)Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/597Design Condense list view2023-10-15T19:23:56ZStefan BusemannDesign Condense list viewcondense the list view: I've a huge screen but see only 2 extensions in list view.
AC:
* Add a button to switch betwenn current view and "condensed view"
* condensed view provides a small list - with Extension title, version number, las...condense the list view: I've a huge screen but see only 2 extensions in list view.
AC:
* Add a button to switch betwenn current view and "condensed view"
* condensed view provides a small list - with Extension title, version number, last upload, 3 latests supporting tagsBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/596Extension RSS feed should create useful links2023-10-25T08:44:41ZMarkus KleinExtension RSS feed should create useful links### Summary
The 50 latest extensions RSS feed generates URLs to extensions, but keep the type= parameter of the RSS feed itself. Hence, the URLs are invalid.
### Steps to reproduce
Look at https://extensions.typo3.org/?type=837
See g...### Summary
The 50 latest extensions RSS feed generates URLs to extensions, but keep the type= parameter of the RSS feed itself. Hence, the URLs are invalid.
### Steps to reproduce
Look at https://extensions.typo3.org/?type=837
See generated URL https://extensions.typo3.org/extension/focuspoint?type=837
### What is the current _bug_ behavior?
Generated detail URLs for extensions are invalid
### What is the expected _correct_ behavior?
URLs must be without `type` parameter.
### Possible fixes
https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/blob/develop/extensions/ter_fe2/Resources/Private/Partials/ExtensionList.rss#L6
Adjust this to a fixed `type=0` .https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/594Exclude private folder from VCS2023-08-19T12:26:58ZTorben HansenExclude private folder from VCSThe `private` folder in the project root contains project specific assets such as `fileadmin` or the `typo3temp` folder, which are symlinked to the `public` folder. All folders in `private` should be excluded from version control.The `private` folder in the project root contains project specific assets such as `fileadmin` or the `typo3temp` folder, which are symlinked to the `public` folder. All folders in `private` should be excluded from version control.Torben HansenTorben Hansenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/587Error 403 when trying to refresh access token via REST API2023-08-15T19:26:28ZElias HäußlerError 403 when trying to refresh access token via REST API### Summary
I try to refresh an access token via TER REST API. The access token was generated with permissions `extension:read` and `extension:write`. All other endpoints work smoothly, but when requesting `/auth/token/refresh`, I keep ...### Summary
I try to refresh an access token via TER REST API. The access token was generated with permissions `extension:read` and `extension:write`. All other endpoints work smoothly, but when requesting `/auth/token/refresh`, I keep getting a 403 response.
Side note: I am able to refresh the exact same token via TER UI at https://extensions.typo3.org/my-access-tokens/refresh.
### Steps to reproduce
1. Create access token with permissions `extension:read` and `extension:write`
2. Try to refresh access token via TER REST API (see curl example below)
### Example URL
Example request:
```bash
curl -X POST https://extensions.typo3.org/api/v1/auth/token/refresh -H "Authorization: Bearer xxx" -d "token=yyy"
```
### What is the current *bug* behavior?
Error 403 response, token is not refreshed.
### What is the expected *correct* behavior?
201 response as written in the [API specification](https://extensions.typo3.org/faq/rest-api#/Auth/refreshToken).
### Relevant logs and/or screenshots
API response:
```
{"status":403,"code":1602754893,"error":"access_denied","error_description":"The user lacks necessary permissions for this endpoint."}
```https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/586Outdated extension metadata from TER REST API2023-08-15T19:28:29ZElias HäußlerOutdated extension metadata from TER REST API### Summary
When requesting extension metadata through TER REST API, the responded information is not always correct. For example, the latest version of EXT:news supports TYPO3 v11 and v12, whereas the API response shows that only TYPO3...### Summary
When requesting extension metadata through TER REST API, the responded information is not always correct. For example, the latest version of EXT:news supports TYPO3 v11 and v12, whereas the API response shows that only TYPO3 v11 is supported.
### Steps to reproduce
Perform request to https://extensions.typo3.org/api/v1/extension/news and compare the response with extension metadata shown at https://extensions.typo3.org/extension/news.
### Example URL
See above.
### What is the current *bug* behavior?
Extension metadata is incorrect – the shown TYPO3 versions do not include all actually supported TYPO3 versions of the latest available version.
### What is the expected *correct* behavior?
The API response should include all actually supported TYPO3 versions.
### Relevant logs and/or screenshots
Current API response:
```json
[
{
"key": "news",
"downloads": 1747634,
"verified": true,
"version_count": 80,
"meta": {
"packagist": "https://packagist.org/packages/georgringer/news",
"composer_name": "georgringer/news",
"forge_link": "https://github.com/georgringer/news",
"repository_url": "https://github.com/georgringer/news",
"external_manual": "",
"paypal_url": "https://www.paypal.me/GeorgRinger/25",
"tags": [
{
"title": "News"
},
{
"title": "Extbase"
},
{
"title": "Fluid"
},
{
"title": "tags"
},
{
"title": "categories"
},
{
"title": "article"
},
{
"title": "Bestpractice"
},
{
"title": "responsive"
},
{
"title": "best-practice"
},
{
"title": "extension"
},
{
"title": "tx-news"
}
]
},
"current_version": {
"title": "News system",
"description": "Versatile news system based on Extbase \u0026 Fluid and using the latest technologies provided by TYPO3 CMS.",
"number": "11.0.0",
"state": "stable",
"category": "fe",
"typo3_versions": [
11
],
"dependencies": {
"typo3": "11.5.19 - 12.9.99",
"php": "7.4.0 - 8.2.99"
},
"conflicts": [],
"downloads": 0,
"upload_date": 1678361701,
"review_state": 0,
"download": {
"composer": "composer req georgringer/news",
"zip": "https://extensions.typo3.org/extension/download/news/11.0.0/zip",
"t3x": "https://extensions.typo3.org/extension/download/news/11.0.0/t3x"
},
"author": {
"name": "Georg Ringer",
"email": "mail@ringer.it",
"company": ""
}
}
}
]
```_Ready for sprinthttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/581Login via my.typo3.org not possible2023-03-31T14:30:46ZOliver MelleLogin via my.typo3.org not possible### Summary
The OAuth2 callback for the login on extensions.typo3.org returns error 503.
### Steps to reproduce
1. Select "Login via my.typo3.org"
2. Enter your login data for my.typo3.org
### URL
https://extensions.typo3.org/oauth2/ca...### Summary
The OAuth2 callback for the login on extensions.typo3.org returns error 503.
### Steps to reproduce
1. Select "Login via my.typo3.org"
2. Enter your login data for my.typo3.org
### URL
https://extensions.typo3.org/oauth2/callback?oauth2-provider=keycloak&logintype=login&state=dd26e890fd386d45b22485ae3928f848&session_state=15ce48e1-659f-4a02-b5d9-8b87a2895acf&code=9fb8f5c6-7f3d-426c-9021-d4605fd92127.15ce48e1-659f-4a02-b5d9-8b87a2895acf.fefaa690-9f55-4439-b376-c31588b11bec
### What is the current *bug* behavior?
Error 503 occurs with the message "Oops, an error occurred! Event: e9ff8e9b0b4f48ae99437cbb4a1e6ab4"
### What is the expected *correct* behavior?
Be logged in into extensions.typo3.org
### Additional information
The account is new. I never visited extensions.typo3.org before.
Browser User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/111.0Oliver MelleOliver Mellehttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/578Add client side validation for version description2023-03-15T14:20:32ZAlexander GreinAdd client side validation for version descriptionSince the sql injection filter of the extension upload form seems to be very restrictive a client side validation of the version description input field would be very helpful.
Otherwise it's always a try and error game to get a new vers...Since the sql injection filter of the extension upload form seems to be very restrictive a client side validation of the version description input field would be very helpful.
Otherwise it's always a try and error game to get a new version uploaded.https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/566Verified Extensions v122023-01-25T15:01:34ZTomas Norre MikkelsenVerified Extensions v12### Problem to solve
When verified extensions like https://extensions.typo3.org/extension/sf_event_mgt are uploaded in a version v12 compatible version only. It should still be possible to mark it as verified in the TYPO3 Backend.
Curr...### Problem to solve
When verified extensions like https://extensions.typo3.org/extension/sf_event_mgt are uploaded in a version v12 compatible version only. It should still be possible to mark it as verified in the TYPO3 Backend.
Currently, this is not possible, as the v12 isn't LTS version yet, and therefore I cannot be saved in the TCA as the select option value is empty.
Response from @frank regaring it:
> Yes, I think showing the compatibility version is a significant benefit. Maybe tag the version with "12" and later with "12 LTS" to differentiate here. Making the fact "compatibility" more visible is very important for early adoption. This could help projects may migrate earlier and easier.
### What does success look like, and how can we measure that?
Extensions already verified for v11, should also be possible to verified for v12 releases, also before v12 is marked as LTS.
**Acceptence Criterias**
* [ ] It should be possible to mark a v12 compatibility only version of an extension as verified.
### Links / referencesThomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/561Add checkbox in form to sign the CoC on extension upload2022-08-17T08:18:41ZThomas LöfflerAdd checkbox in form to sign the CoC on extension uploadAC:
* [ ] Checkbox is added on extension upload form
* [ ] If checkbox is not checked, the extension upload won't workAC:
* [ ] Checkbox is added on extension upload form
* [ ] If checkbox is not checked, the extension upload won't workhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/560Allow declaring multiple authors / multiple donation links2022-08-12T12:26:46ZNikita HovratovAllow declaring multiple authors / multiple donation links### Problem to solve
Sometimes the extension maintainer changes, but the original author should still be displayed as one of the extension authors.
If there are multiple authors, it makes sense to allow for multiple donation links as wel...### Problem to solve
Sometimes the extension maintainer changes, but the original author should still be displayed as one of the extension authors.
If there are multiple authors, it makes sense to allow for multiple donation links as well.
<!--- What problem do we solve? -->
### Further details
Other platforms like packagist and Github already allow multiple authors / donation links. The TER should allow it as well.
<!--- Include use cases, benefits, and/or goals (contributes to our vision?) -->
### Proposal
The composer.json file already contains all needed information in the keys "authors" and "funding". In addition, GitHub funding links could be generated from the .github/FUNDING.yml.
<!--- How are we going to solve the problem? Try to include the user journey! -->
### What does success look like, and how can we measure that?
Authors and donation links are automatically read from composer.json and/or FUNDING.yml and displayed accordingly in the extension detail view.
<!--- 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 -->
### Links / references
Example multiple donation links for the Mask extension: https://packagist.org/packages/mask/maskhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/557Feature request: RSS feed for new/updated extensions2023-09-18T11:49:34ZWolfgang WagnerFeature request: RSS feed for new/updated extensionsIt would be great if the TER could provide an RSS feed to track all changes (new extensions, updated extensions).It would be great if the TER could provide an RSS feed to track all changes (new extensions, updated extensions).BacklogWolfgang WagnerWolfgang Wagner