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/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/563Filtering by TYPO3 version 12 results in an empty list2023-01-26T07:57:55ZEric HarrerFiltering by TYPO3 version 12 results in an empty list### Summary
The "Filter for TYPO3 versions" function in the extension detail view in TER for version 12 currently does not filter the download list correctly. This problem seems to affect all TER extensions that are compatible with TYPO...### Summary
The "Filter for TYPO3 versions" function in the extension detail view in TER for version 12 currently does not filter the download list correctly. This problem seems to affect all TER extensions that are compatible with TYPO3 12.
### Steps to reproduce
If you click on the "12" button under "Filter for TYPO3 versions" in the extension detail view in TER, entries in the download list that are compatible with TYPO3 12 are also removed.
### Example URL
https://extensions.typo3.org/extension/container
### What is the current *bug* behavior?
The filter also removes entries compatible with TYPO3 12.
### What is the expected *correct* behavior?
The filter should display all entries compatible with TYPO3 12.
### Relevant logs and/or screenshots
![Filter-for-TYPO3-version-12-empty](/uploads/4b8a03bbf71af2f1942b211fe5caf038/Filter-for-TYPO3-version-12-empty.png)
### Possible fixes
Since the affected button uses the following HTML code:
```
<input type="radio" name="versions" data-version="12">
```
It seems as if the value "12" should also be output for the entries in the list. Only the value "12 LTS" is currently used here.
```
<tr id="v2.1.0" data-versions="10 LTS,11 LTS,12 LTS" class="table-success" style="">
```BacklogEric HarrerEric Harrerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/556Feature request: Include "verified" state in REST API2022-09-06T07:52:34ZElias HäußlerFeature request: Include "verified" state in REST API### Problem to solve
The REST API endpoint `GET /extension/{key}` (and probably other endpoints as well) should provide the current ["verified" state](https://typo3.com/typo3-cms/verified-extensions-integrations-for-typo3/extensions) of...### Problem to solve
The REST API endpoint `GET /extension/{key}` (and probably other endpoints as well) should provide the current ["verified" state](https://typo3.com/typo3-cms/verified-extensions-integrations-for-typo3/extensions) of an extension.
### Further details
[TYPO3 Badges](https://typo3-badges.dev) is a Symfony application that provides JSON endpoints for Badgen.net and Shields.io to create badges for TYPO3 extensions. Extension metadata is fetched via TER REST API. At the time of this writing, the `GET /extension/{key}` endpoint is used to [fetch metadata](https://github.com/eliashaeussler/typo3-badges/blob/0.4.1/src/Service/ApiService.php#L50).
With [issue #135](https://github.com/eliashaeussler/typo3-badges/issues/135), a new feature was requested: The application should provide an endpoint for the "verified" state of an extension. Since the application itself fetches appropriate information from TER REST API, it's required for the REST API to provide this information.
### Proposal
Include the "verified" state of an extension in the REST API endpoint `GET /extension/{key}` as property `"verified": <true|false>` (or similar):
```diff
{
"key": "container",
"downloads": 177,
+ "verified": true,
"versions_count": 22,
"meta": {
// ...
}
}
```
### What does success look like, and how can we measure that?
As soon as the TER REST API provides the requested information, a pull request in _TYPO3 Badges_ can be submitted. It will provide a new endpoint for the "verified" state of an extension inside the _TYPO3 Badges_ Symfony application.
**Acceptence Criterias**
* [ ] Include "verified" state of extensions in REST API endpoint `GET /extension/{key}`
* [ ] Bump a new REST API version
### Links / references
* Original issue in _TYPO3 Badges_ repo: https://github.com/eliashaeussler/typo3-badges/issues/135BacklogOliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/539Verified Extension State for extensions.typo3.org2021-11-29T18:31:31ZmultanifxVerified Extension State for extensions.typo3.org### Problem to solve
With the concept of verified extensions, we needed a possibility to make verified extensions visible in the TER.
### Further details
Verified Extensions are extensions, which promise next to testing and documentat...### Problem to solve
With the concept of verified extensions, we needed a possibility to make verified extensions visible in the TER.
### Further details
Verified Extensions are extensions, which promise next to testing and documentation also longer and faster support.
To motivate more people, to join the verified extension program, the extensions should be highlightes also in the TER
### Proposal
1) Add an Icon (see attached SVG) to the list and detail view.
As a Suggestion, the icon should be placed together with the word verified
extension_keyx / Stability / (Icon) verified
Another position would be fine too.
2) There should be a filter, to show only verified extensions in the search
This Filter should have:
"Verified Extensions (infoIcon) (number)"
as title
and "Verified" as Filter.
The Icon should be linked to https://typo3.com/typo3-cms/extensions-integrations/what-are-verified-extensions-integrations (online from 25.11)
3) It needs to be possible, to set the state of the verified extensions manually in the backend. It should be set as a flag.
### What does success look like, and how can we measure that?
Success of verified extensions in this context has to sites:
1) the number of verified extensions. it should be a growing number, but this feature is only one part of the full concept.
2) The Number of people using the filter "verified":
If there is a tracking of the usage of the search, this number should be tracked too, and it is hopefully widely used (compared to other filter)
**Acceptence Criterias**
* [ ] The Icon is shown in the list view - Must be fullfilled
* [ ] The Icon is shown in the detail view - Must be fullfilled
* [ ] Searching for verified should filter the list and only display verified extensions - Must be fullfilled
* [ ] An editor must be able to update the state of an extension in the backend - Must be fullfilled
### Links / references
[icon_verified_extension.svg.zip](/uploads/ab918cdef3955c843a505a10fbe8c97d/icon_verified_extension.svg.zip)BacklogThomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/518Filter for distributions2021-05-16T13:51:34ZStefan BusemannFilter for distributions### Problem to solve
As a user, I want to filter for distributions
**Acceptence Criterias**
* [ ] facet options distributions / extensions is available
* [ ] the list is filtered for distributions or extensions, when one the tables ...### Problem to solve
As a user, I want to filter for distributions
**Acceptence Criterias**
* [ ] facet options distributions / extensions is available
* [ ] the list is filtered for distributions or extensions, when one the tables are selectedBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/499Localization Status not shown2021-02-22T13:55:14ZChris MüllerLocalization Status not shown### Summary
For my extension "form_country_select" the localization status is not shown in the detail view in TER. The crowdin project is connected to the extension and an update of the language in TYPO3 itself works correctly.
### Exa...### Summary
For my extension "form_country_select" the localization status is not shown in the detail view in TER. The crowdin project is connected to the extension and an update of the language in TYPO3 itself works correctly.
### Example URLs
* https://extensions.typo3.org/extension/form_country_select/
* https://crowdin.com/project/typo3-extension-formcountryselect
### What is the expected *correct* behavior?
**Acceptence Criterias**
* [x] Translation status is shown in detail view
### Possible fixes
Perhaps it is a mixture of the different writings of the extension and therefore not found:
* Extension key: form_country_select
* Crowdin project name: typo3-extension-formcountryselect
* Composer package: brotkrueml/form-country-selectBacklogChris MüllerChris Müllerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/169Important links should be more visible2020-09-12T13:54:22ZJérémie RoulinImportant links should be more visible## What do you suggest?
The "Extension Manual" link should be more visible. The external repository link should also be more visible. For me it should be placed next to download button. I would do something like that :
![Untitled](/up...## What do you suggest?
The "Extension Manual" link should be more visible. The external repository link should also be more visible. For me it should be placed next to download button. I would do something like that :
![Untitled](/uploads/186e4de92e027299937de6dee34b02a1/Untitled.png)
## Why?
The important links have to be accessible quickly.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/281Scrap tx_ter_extensionqueue2020-08-07T14:29:45ZAndreas WolfScrap tx_ter_extensionqueueThe queue is just used for getting new versions into ter_fe2. This can more easily be done with a signal in ter and a slot in ter_fe2.The queue is just used for getting new versions into ter_fe2. This can more easily be done with a signal in ter and a slot in ter_fe2.BacklogAndreas WolfAndreas Wolfhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/428TER Upload failed2020-07-26T16:39:19ZThorsten HogenkampTER Upload failed### Summary
Uploading new extension releases to TER failed.
### Steps to reproduce
1. Building release as everytime
2. Try to upload extension with helhum/ter-client
3. see failure message
```
In Connection.php line 52:
Error Fetchi...### Summary
Uploading new extension releases to TER failed.
### Steps to reproduce
1. Building release as everytime
2. Try to upload extension with helhum/ter-client
3. see failure message
```
In Connection.php line 52:
Error Fetching http headers
```
### Example URL
https://travis-ci.com/hoogi91/spreadsheets/jobs/273246766
### What is the current *bug* behavior?
Upload to TER fails due to an error in SOAP connection.
### What is the expected *correct* behavior?
Extension is successfully uploaded to TER
**Acceptence Criterias**
* [ ] New tag of extension is uploaded
### Relevant logs and/or screenshots
The error directly occurrs for the soap call in helhum/ter-client:
https://github.com/helhum/ter-client/blob/master/src/Connection.php#L52
### Possible fixes
Maybe this is related to `default_socket_timeout` in the executing php installation but the upload was working before this issue without any modifications on the current php installationBacklogThorsten HogenkampThorsten Hogenkamphttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/252Add Google Sitemap for extensions2020-04-28T06:36:36ZThomas LöfflerAdd Google Sitemap for extensionsIt's just a simple sitemap over the extensions.typo3.org
* [ ] ~~Create page type which calls one action in ExtensionController~~
* [ ] ~~Create action and get all extensions with minimum one version (this version may not have security ...It's just a simple sitemap over the extensions.typo3.org
* [ ] ~~Create page type which calls one action in ExtensionController~~
* [ ] ~~Create action and get all extensions with minimum one version (this version may not have security issues)~~
* [ ] ~~Create Fluid template to create links to detail view of the extensions (one link per line)~~
* [x] Use EXT:seo to create sitemapBacklogThomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/226Add sorting options2020-02-28T16:14:29ZDavid LemaitreAdd sorting optionsAdd sorting options : sort by number of downloads, last uploaded, stability, name, etc.Add sorting options : sort by number of downloads, last uploaded, stability, name, etc.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/308Tags for all compatible TYPO3 versions of an extension2019-11-29T06:43:03ZWolfgang WagnerTags for all compatible TYPO3 versions of an extension## Tags for all compatible TYPO3 versions of an extension
At the moment only the LTS versions are shown as tags in the list of extensions or the single view. I think it would be helpful, especially for unexperienced users, if all compat...## Tags for all compatible TYPO3 versions of an extension
At the moment only the LTS versions are shown as tags in the list of extensions or the single view. I think it would be helpful, especially for unexperienced users, if all compatible versions would be shown as tags. Maybe non-LTS versions could use a different colour (LTS = green, non-LTS maybe light-orange or grey or something)
## Why?
I think it's confusing for some users, if an extension is tagged as compatible with TYPO3 7 LTS oder 8 LTS, but in the dependencies are different versions like 9.1, 9.2 or something.
## Add an use case
An example is (at the moment, 17.01.2018) the Introduction Package https://extensions.typo3.org/extension/introduction/, where the tags and the dependencies don't match.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/219no_cache parameter breaks the detailview (random parameter as well)2019-11-28T16:00:52ZNadir S.no_cache parameter breaks the detailview (random parameter as well)if you add no_cache parameter to a detailview, the page output is not correctly displayed anymore
https://extensions.typo3.org/extension/wfqbe/?no_cache=1
not just no_cache..
https://extensions.typo3.org/extension/wfqbe/?foobar=1 brea...if you add no_cache parameter to a detailview, the page output is not correctly displayed anymore
https://extensions.typo3.org/extension/wfqbe/?no_cache=1
not just no_cache..
https://extensions.typo3.org/extension/wfqbe/?foobar=1 breaks the view as well.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/236Logout not possible from my extensions page on mobile (chrome)2019-11-28T16:00:08ZPhilipp GampeLogout not possible from my extensions page on mobile (chrome)## What was the cause of the issue?
Unexpected post var set (realurl error)
## Steps to reproduce
1. Use mobile chrome on android.
2. Open TER and login
3. Go to my extensions
4. Use menu to click on user icon trying to logout
5. TYPO3 ...## What was the cause of the issue?
Unexpected post var set (realurl error)
## Steps to reproduce
1. Use mobile chrome on android.
2. Open TER and login
3. Go to my extensions
4. Use menu to click on user icon trying to logout
5. TYPO3 error page with realurl error
URL: https://extensions.typo3.org/my-extensions/login/BacklogTomas Norre MikkelsenTomas Norre Mikkelsenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/381Setting up bmack/site-importer to ease the use of the ddev devbox2019-10-16T10:20:10ZTomas Norre MikkelsenSetting up bmack/site-importer to ease the use of the ddev devboxIt would be great if we implement the bmack/site-importer to ease the use of the ddev devbox, so that we don't need to change domain record etc on every new setup..
https://github.com/bmack/site-importerIt would be great if we implement the bmack/site-importer to ease the use of the ddev devbox, so that we don't need to change domain record etc on every new setup..
https://github.com/bmack/site-importerBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/153Lowercase searchterm2019-03-16T14:08:36ZTorben HansenLowercase searchtermWhen searching for e.g. `ke_Search`, the extension with the extension key `ke_search` is not within the result list. Is it possible to lowercase the search term, so cases are ignored?When searching for e.g. `ke_Search`, the extension with the extension key `ke_search` is not within the result list. Is it possible to lowercase the search term, so cases are ignored?Backlog