extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2021-02-15T18:22:51Zhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/156Search results are too big2021-02-15T18:22:51ZFedir RYKHTIKSearch results are too big## What do you suggest?
I would like to suggest to make optimization of search results output and to show at least 10 search results on one page. Google is good example. We could show 5 results x 2 columns.
![image](/uploads/8946f4cadc8...## What do you suggest?
I would like to suggest to make optimization of search results output and to show at least 10 search results on one page. Google is good example. We could show 5 results x 2 columns.
![image](/uploads/8946f4cadc8661634284c3e7719e35ed/image.png)
![image](/uploads/13e4f009786316cce5417efa5fe450c9/image.png)
## Why?
Users hates to scroll to find information.
## Add an use case
At the moment even on 1900x1280pxpx screen we could have only 4 results. Very hard to find the good extension in such way.
![image](/uploads/3dc0bc921f39fd0ad58262d630e9196b/image.png)Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/190list view: one record for row2021-02-15T18:22:48ZAlex Tuverilist view: one record for rowhi good work.
On my opion the list view of tha main page, where the latest extension are listed, should be simplified, with only one record for row, like in the previous repository.
This should be made with a new LINK (column or row disp...hi good work.
On my opion the list view of tha main page, where the latest extension are listed, should be simplified, with only one record for row, like in the previous repository.
This should be made with a new LINK (column or row display).
thank you very much for your work.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/349Idea: Community comments on extensions2022-04-04T17:31:03ZDan Kleine (geb. Dan Untenzu)Idea: Community comments on extensions## What kind of feature do you want?
During a discussion at the latest Usergroup in Dresden we saw the need for comments on extensions. These could provide valuable information to people searching for extensions.
## What are the benefi...## What kind of feature do you want?
During a discussion at the latest Usergroup in Dresden we saw the need for comments on extensions. These could provide valuable information to people searching for extensions.
## What are the benefits? Use Cases?
Specific use cases were: "This extension is not maintained anymore, we switched to XYZ and are happy with it" or "Attention, says it works in 8.7, but doesn't", "Best extension for this use case, love it" or "The maintainer left the company, don't expect any updates anymore". We had such moment at the usergroup, were it came to one's hearing why one popular extension suddenly stopped working.
## Possible solution
Comment section with [pw_comments](https://extensions.typo3.org/extension/pw_comments/).
I like the idea, but shuddered when I heard "comment section", as these need at least some management to prevent violations against Coc and some maintenance efforts against SPAM. → An alternative may be a link to a dedicated Slack channel, since most extension already have a channel and this may be easier to integrate.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/170A much slimmer List-View - One row per Extension2022-04-04T17:34:23ZTorben AschmonsA much slimmer List-View - One row per Extension## What do you suggest?
Make the List much slimmer.
Maybe like:
**EXT-Name** - EXT-Description - EXT-Version/State - Target TYPO3-Versions - Update-Date
Just one row per extension.
## Why?
To have a better and faster overview over mor...## What do you suggest?
Make the List much slimmer.
Maybe like:
**EXT-Name** - EXT-Description - EXT-Version/State - Target TYPO3-Versions - Update-Date
Just one row per extension.
## Why?
To have a better and faster overview over more extension.
## Add an use case
I want to take a look over the recently updated extensions. With a more slimmer List-View I can see more extensions on one sight. So I can scroll through the extensions and see more extensions.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/195delete extension version from TER2021-02-15T18:22:48ZFrank Gerardsdelete extension version from TER## What kind of feature do you want?
make it possible to delete a specific version of an extension from TER (again)
## What are the benefits?
prevent users from downloading faulty code
## Add some use case
realurl_clearcache2 was up...## What kind of feature do you want?
make it possible to delete a specific version of an extension from TER (again)
## What are the benefits?
prevent users from downloading faulty code
## Add some use case
realurl_clearcache2 was uploaded with v2.0.0 (wrong), then changed to 1.0.0 - now, 2.0.0 version cannot be deletedBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/162TER: Suggestion: Do some polishing of design2022-04-04T17:34:22ZbastianbalthasarbuxTER: Suggestion: Do some polishing of designI would like to see some polishing of the design for a major use-case: browsing TER on a desktop machine.
And when I say "design" in this case I just mean to rethink the enormous font-sizes and the bunch of whitespace, which keeps my sc...I would like to see some polishing of the design for a major use-case: browsing TER on a desktop machine.
And when I say "design" in this case I just mean to rethink the enormous font-sizes and the bunch of whitespace, which keeps my scrolling like hell on my 1920x1200 displays.
H1 is 3.something rem, that's 50px high on my screens, and results in letters with a height of 1.3cm ... just 80cm away from my face. That burns-in pixels into my brain!Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/146Content Touchup: "Downloads by Version"2022-04-04T17:34:22ZMarkus TimtnerContent Touchup: "Downloads by Version"This is just a psychological Issue here which bothers me since it was introduced.
Almost always, the line chart shows a downward trend:
![01_line-chart](/uploads/ab5fd09a2c713aab03b3ba80a52fe4a7/01_line-chart.png)
This might hint only ne...This is just a psychological Issue here which bothers me since it was introduced.
Almost always, the line chart shows a downward trend:
![01_line-chart](/uploads/ab5fd09a2c713aab03b3ba80a52fe4a7/01_line-chart.png)
This might hint only negative associations (at least to me) It is not a "very attractive" feature to have so prominently placed on the extension page.
Luckily, there should be an easy fix for this:
A bar chart has the same information value,
whereas it doesn't show such an obvious downward trend:
![01_bar-chart](/uploads/92c3065cbabb21dfd5fb93eb31bce732/01_bar-chart.png)
What do you think?Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/260Add related security bulletin when an extension version is marked as insecure2021-02-15T18:22:28ZJean TraulléAdd related security bulletin when an extension version is marked as insecure## What do you suggest?
When an extension version is marked as insecure, the background of the extension version appear red in the TER website, the download link is removed and the extension version does not appear anymore when searchin...## What do you suggest?
When an extension version is marked as insecure, the background of the extension version appear red in the TER website, the download link is removed and the extension version does not appear anymore when searching in TYPO3 TER BE Module.
I think it could be relevant ta add a link to the particular **[Security Bulletin](https://typo3.org/teams/security/security-bulletins/)** which led to flag that extension version as insecure (to get more information)
Maybe by replacing
| Before | After |
| --- | --- |
| *ATTENTION*: Use at your own risk ! | **ATTENTION** : This extension version has been flagged as insecure by the TYPO3 Security Team, please checkout [**TYPO3-PSA-2017-001**](https://typo3.org/teams/security/security-bulletins/psa/typo3-psa-2017-001/) security bulletin for more information. |
## Why?
It is always interesting to know **why** an extension version has been marked as insecure in my opinon.
## Add an use case
For example, extension [realurl_clearcache2](https://extensions.typo3.org/extension/realurl_clearcache2/) versions has been marked as insecure because of [TYPO3-PSA-2017-001](https://typo3.org/teams/security/security-bulletins/psa/typo3-psa-2017-001/) security bulletin. A link to the security bulletin should be mentionned.
PS : when all versions available are flagged as insecure, **Installation** section shouldn't be hidden (as it allow to download last version) ?
PS2 : for this particular extension ([realurl_clearcache2](https://extensions.typo3.org/extension/realurl_clearcache2/)), why the proposed version in **Installation** section is 1.0.1 and not 2.0.0 ? Shouldn't be the last version proposed ?Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/182Changing some colors ....2021-02-15T18:22:48ZahmadChanging some colors ....Hello,
## What do you suggest?
Changing some colors ....
## Why?
This new Extension Manager has a color design mistake. The first thing comes to eye is "Download version x as Zip" for many times, It's not important, Extension names a...Hello,
## What do you suggest?
Changing some colors ....
## Why?
This new Extension Manager has a color design mistake. The first thing comes to eye is "Download version x as Zip" for many times, It's not important, Extension names are most important but they secondly comes to eye and a user should visualy search for them. It is annoying.
## Add an use case
I suggest to dim the color of the "Download version x as Zip" box.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/385Suggestion: Add core extensions to extension directory2022-04-04T17:34:25ZspetersSuggestion: Add core extensions to extension directory### Problem to solve
* confusion about where to find things
### Further details
Some things have changed: You used to install the core and then you had the extension manager and TER to install additional third party extensions.
Now,...### Problem to solve
* confusion about where to find things
### Further details
Some things have changed: You used to install the core and then you had the extension manager and TER to install additional third party extensions.
Now, since the **subtree split** it is not so different for the end user to install additional core components (system extensions) or third party extensions.
### Proposal
If extensions.typo3.org is nowadays rather used as a catalog (if I understand it correctly), it might be useful to show all, not just the third party extensions.
Of course, the core extensions should be marked as part of the core to underline that they are supported officially by TYPO3.
### What does success look like, and how can we measure that?
* (almost?) all system extensions are searchable in extension directory
* system extensions are clearly marked as system extensions
* if third party extensions depends on system extension, a link is used to link to the sysext in "Dependencies" section
* the composer command is listed for the system extension
## Advantages:
* find everything in one place
* easily find Composer command (or package name) for installing a core extension without having to go to packagist
* dependencies to sysexts could be added as links, e.g. see [rte_ckeditor_image](https://extensions.typo3.org/extension/rte_ckeditor_image/) (depends on rte_ckeditor, this could be a link, as in ext:introduction -> ext:bootstrap_package)
![rte_ckeditor_image](/uploads/b891004c1f19388a8d6fa5b273316495/rte_ckeditor_image.png)
![introduction](/uploads/5f29c3dcb1635b9cb212e2be455db105/introduction.png)
For me, the question is: What is useful for the end user?_Ready for sprinthttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/198Why use big boxes when a list does a much better job?2021-02-15T18:22:52ZChristine RocheltWhy use big boxes when a list does a much better job?First show an overview, then detail on demand.
The new repository wastes a lot of space. Why use big boxes when a list does a much better job?
Please show relevant information like number of downloads, last update...
A "list by" funct...First show an overview, then detail on demand.
The new repository wastes a lot of space. Why use big boxes when a list does a much better job?
Please show relevant information like number of downloads, last update...
A "list by" function would also be helpful: List by
- Number of downloads
- TYPO3 Version
- Relevance
Thank you for your work.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/196Layout suggestions2021-02-15T18:22:47ZpixeldesuLayout suggestionsThe entire layout and sizing of the website feels way too large. _(on screens that are not high resolution/retina)_
It fills the entire screen width for certain device widths (`.container-fluid`) and the headings chosen for the card-tit...The entire layout and sizing of the website feels way too large. _(on screens that are not high resolution/retina)_
It fills the entire screen width for certain device widths (`.container-fluid`) and the headings chosen for the card-titles are way too large as well, wasting a lot of screen space.
Here an example, for a _side-by-side_ view. This first screenshot is the current website as-is.
![Selection_262](/uploads/232478dbb288a2749ea0d86dadec084a/Selection_262.png)
And this is a locally modified version (with Chrome DevTools) just to narrow down a lot of things.
![Selection_263](/uploads/dd907cf63ab30d6e6c3c0b417a812cbf/Selection_263.png)
_(both screenshots capture exactly the same viewport, just from different tabs, no tricking with zoom-levels here :smile: )_
**What I changed:**
* Switched out the `.container-fluid` that a huge part of the site used, replaced it with just `.container` instead.
* Replaced all card headings with `h3` instead of `h2` and all subtitles with `h5` instead of `h4`
* _I also adjusted the padding of the TYPO3 logo, just to properly line up the navigation with the container_
These are not too significant changes to the site layout, but they already make a huge difference compared to what there was before.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/186List view missing info #downloads latest upload2021-02-15T18:22:53ZEdward LenssenList view missing info #downloads latest uploade.g. https://extensions.typo3.org/
In this view I am missing info like #downloads and latest upload. When you search for an extension with many results, this will help you to select the right extension for you.
This would be great fil...e.g. https://extensions.typo3.org/
In this view I am missing info like #downloads and latest upload. When you search for an extension with many results, this will help you to select the right extension for you.
This would be great filter options too for future.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/179Integrate composer2022-04-04T17:34:25ZThomas LöfflerIntegrate composer* Read out composer.json if existing
* Show `composer require` command with package name
* Get download counter from packagist and add it to TER downloads
Relates: #155 #164* Read out composer.json if existing
* Show `composer require` command with package name
* Get download counter from packagist and add it to TER downloads
Relates: #155 #164Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/141Improve PageSpeed Insights results2022-04-04T17:34:24ZGeorg RingerImprove PageSpeed Insights results## What do you suggest?
Current rating: 56/100 for mobile (=poor) and 65/100 (=needs work) for desktop) can be for sure improved.
## Why?
extensions.typo3.org is a often visited page and having good ratings shows that TYPO3 understan...## What do you suggest?
Current rating: 56/100 for mobile (=poor) and 65/100 (=needs work) for desktop) can be for sure improved.
## Why?
extensions.typo3.org is a often visited page and having good ratings shows that TYPO3 understands the importance of such numbers.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/111Add quality information of extension to TER2022-04-04T17:34:24ZThomas LöfflerAdd quality information of extension to TERInformations: https://ter-sonarqube.marketing-factory.de/Informations: https://ter-sonarqube.marketing-factory.de/_Ready for sprinthttps://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/547Use composer/semver for version validation2022-09-09T10:31:24ZgilbertsoftUse composer/semver for version validationWe should consider to use composer/semver for the version validation.We should consider to use composer/semver for the version validation.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/529Allow extension key prefixes 'tt_'2022-05-20T11:40:58ZFranz HolzingerAllow extension key prefixes 'tt_'### Describe the task
In Version 3.6.2 from 2004-07-12 the exensions starting with 'tt' have been removed from TYPO3 and published as external extensions.
So please allow those 'tt_' prefixes for all extension keys.
### What does succe...### Describe the task
In Version 3.6.2 from 2004-07-12 the exensions starting with 'tt' have been removed from TYPO3 and published as external extensions.
So please allow those 'tt_' prefixes for all extension keys.
### What does success look like, and how can we measure that?
The reservation of an extension key tt_example shall be possible.
### Links / referencesBacklog