extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2021-02-15T18:22:53Zhttps://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/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/181Let the counter chart stack download channels2021-02-15T18:22:50ZThomas MayerLet the counter chart stack download channelsFollowing up to #179:
## What kind of feature do you want?
Download counts for each channel (Packagist-composer, TER-composer, TER-EM, TER-manual-download) could be stacked upon each other in the chart.
I suggest to use a single bar f...Following up to #179:
## What kind of feature do you want?
Download counts for each channel (Packagist-composer, TER-composer, TER-EM, TER-manual-download) could be stacked upon each other in the chart.
I suggest to use a single bar for each version whereas the portion of each channel gets a different color. Now that the channels are stacked on each other the totals are still visible (overall, that's still the most valuable information).
Now that highcharts supports stacking, it should still be of use.
## What are the benefits?
We would see which download channel is used by users.
## Alternative
Highcharts also supports line charts (with colored areas) which can be stacked.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/178Make specific versions clickable and show version specific information2021-02-15T18:22:53ZThomas MayerMake specific versions clickable and show version specific information## What kind of feature do you want?
The version list hover-highlights a specific version which is older than the latest version. However, when the old version is clicked, nothing happens.
I suggest to let users click on specific (old)...## What kind of feature do you want?
The version list hover-highlights a specific version which is older than the latest version. However, when the old version is clicked, nothing happens.
I suggest to let users click on specific (old) versions. Then, all the information is displayed specific to that version, especially the dependencies of that version (Not just TYPO3 version, but also PHP version and extensions (or composer packages) the extension depends on).
![Auswahl_359](/uploads/42b6a857cbb714d8b98d568164a7bf11/Auswahl_359.png)
![Auswahl_360](/uploads/201f685e5eeac1d8e8861e7ddfc29142/Auswahl_360.png)
The [URL](https://extensions.typo3.org/extension/metaseo/) could still default to the latest version whereas for different version a specific URL should be used (e.g. `https://extensions.typo3.org/extension/metaseo/TER-2.1.0`).
To add some consistency, it would then also be possible to point to the corresponding version of the manual.
## What are the benefits?
Currently, the dependencies of old versions cannot be displayed to the user. That should not be, now that the information itself is already available.
On top of that, documentation might differ between versions so that users need to choose the right version every time.
## Add some use case
For MetaSEO, we have a version 3.0.0 for TYPO3 8.7 and a version 2.1.0 for TYPO3 6.2 - 7.6. Both branches are still maintained so that version 2.1.0 is just as relevant as 3.0.0. However, the dependencies between both versions are different and this is not visible to users (we still maintain version 2.1.0 against PHP 5.3 to still support TYPO3 6.2 which initially got released against PHP 5.3).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/166Collapse narrow search on mobile2021-02-15T18:22:48ZJérémie RoulinCollapse narrow search on mobile## What do you suggest?
The "Narrow search" should be collapsible on mobile.
## Why?
When going on TER users are interested by extensions so it should come first. For the moment the first thing we see on mobile is the "Narrow search" ...## What do you suggest?
The "Narrow search" should be collapsible on mobile.
## Why?
When going on TER users are interested by extensions so it should come first. For the moment the first thing we see on mobile is the "Narrow search" which is not very important I guess.Backloghttps://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/157Layout Button vs. Badge2022-04-04T17:34:24ZFelix KoppLayout Button vs. BadgeButtons and info badges have identical styling. Hard to distinct between click and info areas.
Badge might be used in html.![Screen_Shot_2017-08-24_at_15.35.48](/uploads/e1976cfd3391170f404e82c99e55aa4c/Screen_Shot_2017-08-24_at_15.35.4...Buttons and info badges have identical styling. Hard to distinct between click and info areas.
Badge might be used in html.![Screen_Shot_2017-08-24_at_15.35.48](/uploads/e1976cfd3391170f404e82c99e55aa4c/Screen_Shot_2017-08-24_at_15.35.48.png)
![Screen_Shot_2017-08-24_at_15.36.21](/uploads/60dfbc4fc1d4c5295089722db1070e7f/Screen_Shot_2017-08-24_at_15.36.21.png)Backloghttps://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/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/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/113Downloads by time chart2021-02-15T18:23:06ZPeter KraumeDownloads by time chartThe downloads by version chart has some drawbacks:
- if an extension has no new releases over a long time, the download counter for the last version might be very high
- if the update frequency changes from seldom to often the chart mig...The downloads by version chart has some drawbacks:
- if an extension has no new releases over a long time, the download counter for the last version might be very high
- if the update frequency changes from seldom to often the chart might lead to the conclusion that the extension isn't requested that much.
For those searching for an extension it might be more useful to know, whether the general interest into an extension increased or decreased over time. It doesn't matter that much which version was downloaded.
A good example is the Solr extension. I assume that average download count didn't decrease that much!
![solr](/uploads/2a8019d954b94d72279c217a68acf996/solr.png)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/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 / references