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/commentsBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/238Fix some lapses in the webserver/HTTPS configuration2021-02-15T18:22:32ZPhilipp GampeFix some lapses in the webserver/HTTPS configuration## What do you suggest?
Get a perfect track record in security checks
https://www.hardenize.com/report/extensions.typo3.org/1505460297#summary
## Why?
Because ;)
## Add an use case
Have a secure web## What do you suggest?
Get a perfect track record in security checks
https://www.hardenize.com/report/extensions.typo3.org/1505460297#summary
## Why?
Because ;)
## Add an use case
Have a secure webBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/240Integrate Sonarcube in TER search2022-04-04T17:34:23ZPeter KraumeIntegrate Sonarcube in TER searchMarketing Factory provides a Sonarcube installation which tests all extensions uploaded to TER:
https://ter-sonarqube.marketing-factory.de/projects
In a first step it would be very helpful to add a link "Code Analysis" to the sidebar in...Marketing Factory provides a Sonarcube installation which tests all extensions uploaded to TER:
https://ter-sonarqube.marketing-factory.de/projects
In a first step it would be very helpful to add a link "Code Analysis" to the sidebar in the detail view which leads to the single view of sonarcube for the specific extension.
For the long term future it would be awesome if we can provide our own Sonarcube installation with an official rule set. Maybe it's even possible to directly integrate the rating of an extension within the TER detail view.
This feature would help people who evaluate different extensions to make an easier decision which extension to take.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/251Provide examples how to create code inspections and better code quality2022-04-04T17:34:22ZTobias GülzowProvide examples how to create code inspections and better code qualityHi everyone.
## What kind of feature do you want?
As an extension developer, I want to make sure that my extension does not get negative badges assigned from code inspection.
I also want to make sure that positive badges get assigned.
#...Hi everyone.
## What kind of feature do you want?
As an extension developer, I want to make sure that my extension does not get negative badges assigned from code inspection.
I also want to make sure that positive badges get assigned.
## What are the benefits?
The code quality will increase significantly, if developers can check their code, before they upload their extension.
## Add some use case
1.) Write a lot of code for your extension.
2.) Do a lot of testing.
3.) Let code inspection analyse the code.
4.) Fix all findings that can be fixed.
5.) Upload another release.
TobiBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/257Extension Installation Workflow2022-04-04T17:34:23ZThomas LöfflerExtension Installation WorkflowSuggestion:
* Make a dropdown instead of a download button
* Rename it to `Install via`
* In the dropdown there are these options: `ZIP file`, `T3X file` and `composer`
* When clicking one of the option there will open a modal with the ...Suggestion:
* Make a dropdown instead of a download button
* Rename it to `Install via`
* In the dropdown there are these options: `ZIP file`, `T3X file` and `composer`
* When clicking one of the option there will open a modal with the installation How-Tos (currently as collapsables)
* In the background the file will be downloaded (if ZIP or T3X)
* When clicking on `composer` the `composer require <package>` command will be displayed
* In the version history the composer command will be appended with the versionBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/258Change database structure to save download numbers with the point of time2022-08-12T11:44:46ZThomas LöfflerChange database structure to save download numbers with the point of timeCurrently the download numbers are stored in the version and we have no possibility to look when the download happened.Currently the download numbers are stored in the version and we have no possibility to look when the download happened.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/301Fix invalid/suspicious version strings in extensions.xml.gz2022-04-04T16:14:48ZMichael SchamsFix invalid/suspicious version strings in extensions.xml.gzAssuming, the format of a **valid** version string is `x.y.z`, where each element is a numeric value between `0` and `999`, file `extensions.xml.gz` contains some invalid/suspicious entries. I assume the issues exist in the underlying da...Assuming, the format of a **valid** version string is `x.y.z`, where each element is a numeric value between `0` and `999`, file `extensions.xml.gz` contains some invalid/suspicious entries. I assume the issues exist in the underlying data storage rather than in the creation logic that generates the XML file.
* `EXT:dam` contains an invalid version string: "1.3.2-dev"
* `EXT:bootstrap_package` contains an invalid version string: "6.2.3.2"
* `EXT:bootstrap_package` contains an invalid version string: "6.2.2.1"
* `EXT:bootstrap_package` contains an invalid version string: "6.2.3.0"
* `EXT:bootstrap_package` contains an invalid version string: "6.2.3.1"
* `EXT:tweet_this` contains an empty version string.
* `EXT:webdav` contains an invalid version string: "2.02"
* `EXT:generic_gallery` contains an invalid version string: "1.0.1-dev"
* `EXT:ke_search` contains an invalid version string: "1.7.0DEV"
* `EXT:libconnect` contains an invalid version string: "EZB: jetzt"
* `EXT:go_maps_ext` contains an invalid version string: "1.5"
* `EXT:metadata` contains an invalid version string: "2.1.0-dev"
* `EXT:groupdocs_viewer` contains an invalid version string: "1.0"
* `EXT:flat` contains an invalid version string: "6.2.0.1"
* `EXT:moc_message_queue` contains an invalid version string: "1.0"
* `EXT:kss_tmpl_gumby` contains an invalid version string: "2.5"
* `EXT:askom` contains an invalid version string: "1.0"
* `EXT:gsexy` contains an invalid version string: "2.0.2 - v.1"
* `EXT:gsexy` contains an invalid version string: "2.0.3 - v.1"
* `EXT:gsexy` contains an invalid version string: "2.0.4 - v.1"
* `EXT:beuserlistexport` contains an invalid version string: "0.0.2.2"
* `EXT:trb_ce_div` contains an invalid version string: "1.0"
* `EXT:trb_ce_icon` contains an invalid version string: "1.0"
* `EXT:trb_ce_map` contains an invalid version string: "1.0"
* `EXT:trb_ce_text` contains an invalid version string: "1.0"
* `EXT:trb_ce_textpic` contains an invalid version string: "1.0"
* `EXT:trb_pi_news` contains an invalid version string: "1.0"
* `EXT:trb_pi_team` contains an invalid version string: "1.0"
* `EXT:trb_pi_portfolio` contains an invalid version string: "1.0"
* `EXT:context_hints` contains an invalid version string: "1.2.0-dev"
* `EXT:jquery_smartbanner` contains an invalid version string: "1.0"
* `EXT:fb_reports` contains an invalid version string: "0.7.0-dev"
* `EXT:layersliderlight` contains an invalid version string: "5.3.3.1"
* `EXT:layersliderlight` contains an invalid version string: "5.3.3.2"
* `EXT:layersliderlight` contains an invalid version string: "5.3.3.3"
* `EXT:layersliderlight` contains an invalid version string: "5.3.3.4"
* `EXT:layersliderlight` contains an invalid version string: "5.3.3.5"
* `EXT:layersliderlight` contains an invalid version string: "5.3.3.6"
* `EXT:groupdocs_annotation_for_net` contains an invalid version string: "1.0"
* `EXT:speciality_distribution` contains an invalid version string: "1.1.0-dev"
* `EXT:wiris_plugin` contains an invalid version string: "3.53.3-1157"
* `EXT:secsign` contains an invalid version string: "1.1"BacklogThomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/302Fix invalid/suspicious extension keys in extensions.xml.gz2022-04-04T16:14:48ZMichael SchamsFix invalid/suspicious extension keys in extensions.xml.gzAssuming, a **valid** extension key must not contain upper-case letters, file `extensions.xml.gz` contains some invalid/suspicious entries. I assume the issues exist in the underlying data storage rather than in the creation logic that g...Assuming, a **valid** extension key must not contain upper-case letters, file `extensions.xml.gz` contains some invalid/suspicious entries. I assume the issues exist in the underlying data storage rather than in the creation logic that generates the XML file.
* invalid extension key: `flvStreamPlayer`
* invalid extension key: `meta_CAS`
* invalid extension key: `AjaxChat`
* invalid extension key: `tom_FMENU`
* invalid extension key: `dmc_highPerformance`
* invalid extension key: `Oblady_questionnaire`
* invalid extension key: `SBuniplug`
* invalid extension key: `SBumfrage`
* invalid extension key: `SBbanner`
* invalid extension key: `theFormEval`
* invalid extension key: `theFormConcept`
* invalid extension key: `lilURL`
* invalid extension key: `RealURL`
* invalid extension key: `Vertretungsplan`BacklogMichael SchamsMichael Schamshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/303Expired extension is not deleted properly2022-04-04T16:13:20ZThomas LöfflerExpired extension is not deleted properly## What was the cause of the issue?
Extension key was accidently expired and removed.
Trying to get the extension key again was not successful.
## Steps to reproduce
1. Let an extension expire and delete
1. Try to get the extension ke...## What was the cause of the issue?
Extension key was accidently expired and removed.
Trying to get the extension key again was not successful.
## Steps to reproduce
1. Let an extension expire and delete
1. Try to get the extension key again
## Output of error log
An extension with this key already exists.
## Add some screenshotsBacklogThomas LöfflerThomas Löfflerhttps://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/368Smarter default sorting2022-04-04T17:32:47ZMathias BrodalaSmarter default sorting## What do you suggest?
It would be really useful if the default sorting of extensions upon search was a bit smarter. This means that properties really relevant to humans should have a higher weight:
* number of downloads
* date of las...## What do you suggest?
It would be really useful if the default sorting of extensions upon search was a bit smarter. This means that properties really relevant to humans should have a higher weight:
* number of downloads
* date of last update
* number of supported TYPO3 LTS versions
* (possibly more)
This is slightly related to #168 but aims at the default sorting.
## Why?
Users should get a useful suggestion for their searches. It is safe to assume that anyone who actually searches by terms instead of directly opening the detail page of an extension doesn't really know the most common and proven solutions.
## Add an use case
A [search for *registration*](https://extensions.typo3.org/?L=0&id=1&tx_solr%5Bq%5D=registration) currently yields the following result:
1. `registration`
2. `agency`
3. `agency_tt_address`
4. `sf_event_mgt`
5. `slub_events`
6. `sf_register`
7. `autobeuser`
8. `sr_feuser_register`
9. `dated_news`
10. `femanager`
11. ...
You can clearly see the mixed "quality" of the search results. The top hit is `registration` due to the exact name match but it's probably the extension most unlikely to solve the issue at hand since it is alpha, outdated and officially does not support any TYPO3 version. Instead `femanager` and `sr_feuser_register` should be the top hits, the number of downloads support this assumption.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/436Integrate PHP Filter2022-04-04T17:35:19ZAlexander NostadtIntegrate PHP Filter### Problem to solve
Currently one cannot filter by a certain PHP Version. However, perhaps I need an extension which supports an older PHP Version because it's for whatever reason impossible to upgrade T3 right now or I do want ext. on...### Problem to solve
Currently one cannot filter by a certain PHP Version. However, perhaps I need an extension which supports an older PHP Version because it's for whatever reason impossible to upgrade T3 right now or I do want ext. only which support latest PHP version.
### Further details
Integrator can search more easily for extensions which meets the PHP requirement of a certain T3 instance.
### Proposal
A new filter on the left, just like T3 LTS.
**Which PHP versions to show?**
I can imagine two ways of which the first is more easy to implement:
* a static list with PHP versions (5.6, 7.0, 7.1, ...)
* determined based on the dependencies by the ext.
* most likely we will end with a huge list of php versions. So, to reduce that the versions could be trimmed to 5.6, 7.0, 7.1, ... So, the static list would be a dynamic list. I would update the dynamic list once a (new) extension version is uploaded. Currently that's only via the Website possible I think.
### What does success look like, and how can we measure that?
<!--- 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 -->
**Acceptence Criterias**
* [ ] There is a working PHP filter
*There might be more. Depending on how the PHP filter should be managed.*
### Links / referencesBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/449Add composer require --dev to the detail view2022-04-04T17:35:21ZAlexander NostadtAdd composer require --dev to the detail view### Problem to solve
Some extensions are expected to installed / used in dev context only. The current snippet automatically installs in prod mode.
### Further details
The benefit would be to install more quickly libs in dev mode. No...### Problem to solve
Some extensions are expected to installed / used in dev context only. The current snippet automatically installs in prod mode.
### Further details
The benefit would be to install more quickly libs in dev mode. No need anymore to adjust the copied snippet.
### Proposal
We could either go the easy way and show the additional snippet always or allow an extension owner to flag the extension as dev extension which causes the proper snippet to be rendered.
Following should be discussed further:
1) Do we want to show the --dev snippet always
2) If 1 is answered with no, should an ext. owner flag the ext. as dev-ext.? Also, if an ext. is flagged as dev, should we still display the prod snippet?
### What does success look like, and how can we measure that?
TBD after discussion.
**Acceptence Criterias**
* [ ] TBD
### Links / referencesBacklogThomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/491Token ID list2022-11-18T12:47:19ZgilbertsoftToken ID list### Problem to solve
Currently a token disapears after the creation and the users have no idea about the created tokens and the assigned rights and extensions.
### Further details
<!--- Include use cases, benefits, and/or goals (contr...### Problem to solve
Currently a token disapears after the creation and the users have no idea about the created tokens and the assigned rights and extensions.
### Further details
<!--- Include use cases, benefits, and/or goals (contributes to our vision?) -->
### Proposal
It would be great to have an overview of the created tokens (names) and the assigned rights and extensios. Also a button to revoke a token would be great.
### What does success look like, and how can we measure that?
<!--- 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 -->
Example from Github Secrets:
![image](/uploads/ffa0189d03559fef00e948880e8f8c29/image.png)
**Acceptence Criterias**
* [ ] simple list of token names
* [ ] optional, the assigned rights and extensions
* [ ] optional, a revoke button
### Links / referencesBacklogBenni MackOliver BartschBenni Mackhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/509Downloadstatistic of extensions2023-04-03T15:53:04ZGernot PloinerDownloadstatistic of extensions1) Downloads by months:
For example EXT:mask (from 17.02.2021):
Packagist says: Last 30 days 15 .968
T3O says (from Packagist in FEB 2021): 15.246
This does not match. February should have about 8.500 downloads today (17 * ~500).
ht...1) Downloads by months:
For example EXT:mask (from 17.02.2021):
Packagist says: Last 30 days 15 .968
T3O says (from Packagist in FEB 2021): 15.246
This does not match. February should have about 8.500 downloads today (17 * ~500).
https://extensions.typo3.org/extension/mask/
https://packagist.org/packages/mask/mask/stats
2) Total Downloads (in right column on T3O):
The total download amount does not match (25.02.2021):
Packagist says: 303.627
T3O says: 72.660
T3O should be higher, because the downloads from T3O and Extensionmanager are counted too.
**Possible solutions**
ad 1)
You told me on Slack, that T3O counts only packagist-downloads from versions, which are also in TER. But the result is confusing. A quick solution can be, to explain this difference to users e.g. in a tooltipp.
But I think, that users are not interested in this difference. They want to know, how much an extension is downloaded at all. So the same numbers as on packagist (+TER numbers) would be great.
ad 2)
I'm sure here is also a missing explanation and not a bug. But I would prefer the same numbers here too.
Instead of:
```
Downloads
72,660
```
I would like to have:
```
Downloads
100.000 Extensionmanager
72.660 T3O
303.627 Packagist (i)
------------------------------
476.287 Total
```BacklogGernot PloinerGernot Ploinerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/512TYPO3 CMS Dependecies wrong links2022-04-04T17:06:49ZTomas Norre MikkelsenTYPO3 CMS Dependecies wrong linksSteps to reproduce:
1. Go to e.g. https://extensions.typo3.org/extension/legacy_collections
2. Scroll down to dependencies on the right hand side
3. Frontend is linked to https://extensions.typo3.org/extension/frontend
Expected Behavio...Steps to reproduce:
1. Go to e.g. https://extensions.typo3.org/extension/legacy_collections
2. Scroll down to dependencies on the right hand side
3. Frontend is linked to https://extensions.typo3.org/extension/frontend
Expected Behaviour:
Would expect typo3/cms-"extensions" to be linked, only non-system extensions.
![Dependencies](/uploads/a51eed04dd0b82ceae52a4ccc0e393b4/Dependencies.png)Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/517Upload of Extensions with Emoji(🔺🟨🟢) in the ext_emconf.php title2022-04-04T17:31:05ZMatthias VogelUpload of Extensions with Emoji(🔺🟨🟢) in the ext_emconf.php title### Problem to solve
Allow emojis in the title of Extensions. Because it is 2021 😀 and makes our lives colorful 🎨
### Further details
Currently we get an error on Upload if the extension title has an emoji in it:
```
Error 0: An excep...### Problem to solve
Allow emojis in the title of Extensions. Because it is 2021 😀 and makes our lives colorful 🎨
### Further details
Currently we get an error on Upload if the extension title has an emoji in it:
```
Error 0: An exception occurred while executing 'INSERT INTO `tx_terfe2_domain_model_version` (`pid`, `crdate`, `tstamp`, `extension`, `title`, `description`, `author`, `version_number`, `version_string`, `upload_date`, `upload_comment`, `file_hash`, `download_counter`, `frontend_download_counter`, `state`, `em_category`, `create_dirs`, `uploadfolder`, `clear_cache_on_load`, `review_state`, `manual`, `has_manual`, `software_relations`, `t3x_file_size`, `zip_file_size`, `composer_info`, `compatible_typo3_versions`, `dependencies`, `authorname`, `authoremail`, `authorcompany`) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)' with params [2, 1620981173, 1620981173, 20747, "Web Vitals Tracker \ud83d\udd3a\ud83d\udfe8\ud83d\udfe2", "Real Measurement Web Vitals Statistic for your TYPO3", "36626", 1000000, "1.0.0", 1620981173, "first working version", "6be7963f94e68d443f79770ea0585e0b", 0, 0, "stable", "fe", "", 0, 0, 0, "", 0, 0, 61568, 0, "{\"autoload\":{\"psr-4\":{\"Kanti\\\\WebVitalsTracker\\\\\":\"Classes\"}},\"name\":\"kanti\\\/web-vitals-tracker\"}", "", "[{\"kind\":\"depends\",\"extensionKey\":\"typo3\",\"versionRange\":\"11.2.0 - 11.5.99\"},{\"kind\":\"suggests\",\"extensionKey\":\"dashboard\",\"versionRange\":\"11.2.0 - 11.5.99\"}]", "Matthias Vogel", "typo3@kanti.de", ""]: Incorrect string value: '\xF0\x9F\x94\xBA\xF0\x9F...' for column `extensions-prod`.`tx_terfe2_domain_model_version`.`title` at row 1
```
Tried with the title "Web Vitals Tracker 🔺🟨🟢"
### Proposal
a Possible solution could be to change the Database to utf8mb4 encoding
I found this Article (in german) https://www.hydroxi.de/utf8-vs-utf8mb4/
### What does success look like, and how can we measure that?
<!--- 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 -->
**Acceptence Criterias**
* [ ] You can upload an extension that contains emoji's
* [ ] and this title will be displayed correctly everywhere.
### Links / references
- https://www.hydroxi.de/utf8-vs-utf8mb4/
- https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.5/Feature-80398-Utf8mb4OnMysqlByDefaultForNewInstances.html
- https://docs.typo3.org/m/typo3/guide-installation/9.5/en-us/Upgrade/Preparation/Index.html#upgrade-hints-for-version-9Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/521Provide JSON files with extension information that work for specific or all T...2022-04-04T17:31:04ZThomas LöfflerProvide JSON files with extension information that work for specific or all TYPO3 versionsExamples:
`fileadmin/ter/extensions.json` => All extensions<br>
`fileadmin/ter/extensions.v9.json` => All extensions working with TYPO3 v9<br>
`fileadmin/ter/extensions.v10.json` => All extensions working with TYPO3 v10
Additionally ad...Examples:
`fileadmin/ter/extensions.json` => All extensions<br>
`fileadmin/ter/extensions.v9.json` => All extensions working with TYPO3 v9<br>
`fileadmin/ter/extensions.v10.json` => All extensions working with TYPO3 v10
Additionally add a `json-file.md5` file for fast check if file has changedBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/522Re-index extension after change of documentation link2023-06-15T19:18:04ZThomas LöfflerRe-index extension after change of documentation linkIf there is a change in the documentation link (currently fetched by intercept.typo3.com) there is a need of re-indexing.If there is a change in the documentation link (currently fetched by intercept.typo3.com) there is a need of re-indexing.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/525Email notification on token expiration2022-04-04T17:31:04ZRudy GnoddeEmail notification on token expiration### Problem to solve
Access tokens expire after at most a year. It would be handy if there was an email notification when a token is about to expire, so users can update them.
### What does success look like, and how can we measure tha...### Problem to solve
Access tokens expire after at most a year. It would be handy if there was an email notification when a token is about to expire, so users can update them.
### What does success look like, and how can we measure that?
**Acceptence Criterias**
* [ ] Email notification when token is about to expire
* [ ] Email notification when token has expiredBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/526Create abstract notification command where all automatic notification are reg...2022-04-04T17:31:06ZThomas LöfflerCreate abstract notification command where all automatic notification are registered## Problem
Many commands that notify the user of specific
## Solution
One command which runs regularly and all other notification service can hook into it## Problem
Many commands that notify the user of specific
## Solution
One command which runs regularly and all other notification service can hook into itBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/527Add pre-release check when releasing extension2022-04-04T17:31:06ZThomas LöfflerAdd pre-release check when releasing extensionThere should be some checks for basic things when there is an extension release (via form, SOAP or REST)
1. `composer.json` file (?) and mandatory fields inside
1. `extension-key`
2. `vendor` (`TYPO3` not allowed)
3. `require` ...There should be some checks for basic things when there is an extension release (via form, SOAP or REST)
1. `composer.json` file (?) and mandatory fields inside
1. `extension-key`
2. `vendor` (`TYPO3` not allowed)
3. `require` includes `typo3/cms-core`
4. Link to the repository (?)
5. `autoload` information if Classes folder exists (?)
2. Documentation exists in any way (Readme file, Documentation folder including not only fake)
Additionally provide this as GitHub Action, GitLab job, etc. for automatic checks before even tags are set.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 / referencesBackloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/546Validate composer.json on extension upload2022-01-15T20:43:22ZThomas LöfflerValidate composer.json on extension upload## Background
TYPO3 moves more and more into "composer first". [This feature](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/11.4/Feature-94996-ConsiderAllComposerInstalledExtensionsAsActive.html) is describing it best.<br...## Background
TYPO3 moves more and more into "composer first". [This feature](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/11.4/Feature-94996-ConsiderAllComposerInstalledExtensionsAsActive.html) is describing it best.<br>
In TER we still validate only the ext_emconf.php file and do only check the existence of a composer.json and some of its content.
## ACs
* [ ] Add a check for a valid composer.json on extension upload (similar to [this minimal composer.json](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/ComposerJson/Index.html#minimal-composer-json))
* [ ] name is set
* [ ] description is set
* [ ] license is set
* [ ] type is `typo3-cms-extension`
* [ ] extras/typo3-cms/extension-key is set
* [ ] requires `typo3/cms-core`
* [ ] Return a warning if composer.json is invalid or not existing on extension upload until date XX.XX.2022
* [ ] Return an error and deny extension upload after date XX.XX.2022Backloghttps://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/548TER REST API throws exception on TYPO3 version although the version is given2022-05-15T19:23:44ZChristian BuelterTER REST API throws exception on TYPO3 version although the version is givenWhen uploading the Extension "access_keys" via tailor the API throws an exception that no full version for TYPO3 Core is given although a version is given.
Uploading manually into the TER works.
## Exception
```
array (
0 => '{"stat...When uploading the Extension "access_keys" via tailor the API throws an exception that no full version for TYPO3 Core is given although a version is given.
Uploading manually into the TER works.
## Exception
```
array (
0 => '{"status":400,"code":1604923182,"error":"invalid_request","error_description":"No full version for TYPO3 Core given."}',
)
```
The exeception seems to be generated here:
https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/blob/develop/extensions/ter_rest/Classes/Service/Extension/VersionService.php#L313
## em_conf.php
The full `em_conf.php` is:
https://gitlab.com/codingms/typo3-public/access_keys/-/blob/main/ext_emconf.php
```
<?php
$EM_CONF['access_keys'] = [
'title' => 'Access-Keys for Backend',
'description' => '',
'category' => 'backend',
'author' => 'Thomas Deuling',
'author_email' => 'typo3@coding.ms',
'state' => 'alpha',
'internal' => '',
'uploadfolder' => '0',
'createDirs' => '',
'clearCacheOnLoad' => 0,
'version' => '1.0.1',
'constraints' => [
'depends' => [
'typo3' => '10.4.0-11.5.99',
],
'conflicts' => [
],
'suggests' => [
],
],
];
```BacklogOliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/554Question: REST API - query extensions2022-05-17T17:12:15ZOliver HaderQuestion: REST API - query extensions```
GET /api/v1/extension?page=1&per_page=50&filter%5Btypo3_version%5D=10
```
I was using above endpoint and foundation in order to fetch all extensions that
* are at least compatible with TYPO3 v10 (`typo3_version>=10`)
* that referen...```
GET /api/v1/extension?page=1&per_page=50&filter%5Btypo3_version%5D=10
```
I was using above endpoint and foundation in order to fetch all extensions that
* are at least compatible with TYPO3 v10 (`typo3_version>=10`)
* that reference to a composer name (`meta/composer_name<>''`)
Thanks in advance for any feedback, how to retrieve that data.BacklogOliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/555Provide TOP 10 statistics for TYPO3 newsletter2022-05-15T19:23:29ZAlexander NitscheProvide TOP 10 statistics for TYPO3 newsletter### Problem to solve
The newsletter has space to fill in every edition and the reader is expecting interesting topics around TYPO3.
### Proposal
Integrate TER statistics into the newsletter to inspire the reader. It would be cheap to ...### Problem to solve
The newsletter has space to fill in every edition and the reader is expecting interesting topics around TYPO3.
### Proposal
Integrate TER statistics into the newsletter to inspire the reader. It would be cheap to achieve but an interesting part nevertheless and it further increases traffic at the store. For example, it would be interesting to have the following statistics
1. the top 10 of extensions regarding download rates for the current LTS only (with comparison to ranking of last newsletter)
2. the top 10 of extensions regarding download rates summarized over all versions of ELTS or LTS series (with comparison to ranking of last newsletter)
3. the top 10 of extensions regarding the increase of download rates for the current LTS only (having passed a certain threshold, with comparison to ranking of last newsletter)
4. the top 10 of extensions regarding the increase of download rates summarized over all versions of current ELTS or LTS (having passed a certain threshold, with comparison to ranking of last newsletter)
presented in tables like the book bestseller tables and linking the extension names into the store.
### What does success look like, and how can we measure that?
Increased traffic in TER with a benefit for the most popular extensions. Guidance for new TYPO3 community members in choosing the right solution for their specific challenges.
### Additional notes
The statistics could be also published automatically as content elements at the TER page in perspective.Backloghttps://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 Wagnerhttps://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/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)Backlog