extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2021-02-15T18:23:06Zhttps://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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/202Show alternatives to outdated extensions2021-02-15T18:22:53ZThomas MayerShow alternatives to outdated extensions## What kind of feature do you want?
In the detail view, alternatives to an outdated extension could be shown up.
For instance, I'll leave open how this can be done.
One way to do this would be to use the tags and to determine a notion...## What kind of feature do you want?
In the detail view, alternatives to an outdated extension could be shown up.
For instance, I'll leave open how this can be done.
One way to do this would be to use the tags and to determine a notion of similarity towards other extensions.
Another way would be to let maintainers explicitly specify which extensions can be migrated to their extension (similar to the specification of incompatibility). The latter should then also take versions into account (from_version/to_version) which maybe overcomplicates this approach.
Another way to do this is to use frequent pattern mining based upon the sequence of page visits, thereby answering which (alternative) extension is likely to be downloaded after visiting an outdated extension.
An easy catch would be to just point to the TER search page, thereby querying for the tags of the outdated extension.
## What are the benefits?
- Show up that there is an alternative.
- Trick users into supported extensions which receive security updates.
## Add some use case
E. g. the outdated extension [tq_seo](https://extensions.typo3.org/extension/tq_seo/) can be seemlessley upgraded to [metaseo](https://extensions.typo3.org/extension/metaseo/) via a documented [migration path](https://docs.typo3.org/typo3cms/extensions/metaseo/AdministratorManual/Index.html#migration-from-extension-tq-seo).Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/203Display number of downloaded in list page2021-02-15T18:22:54ZJainish SenjaliyaDisplay number of downloaded in list pageDisplay number of download extension in list page. SO user can identify easily which extension are mostly usedDisplay number of download extension in list page. SO user can identify easily which extension are mostly usedBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/237Create test suites2021-02-15T18:22:33ZThomas LöfflerCreate test suitesWe need to run tests before merging.
1. Acceptance tests
1. Functional tests
1. Unit tests
Examples: https://gitlab.com/derhansen/commentsWe need to run tests before merging.
1. Acceptance tests
1. Functional tests
1. Unit tests
Examples: https://gitlab.com/derhansen/commentsBacklog