extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2022-04-04T17:32:47Zhttps://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/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/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/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/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/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/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/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/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/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/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/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/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/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/198Why use big boxes when a list does a much better job?2021-02-15T18:22:52ZChristine RocheltWhy use big boxes when a list does a much better job?First show an overview, then detail on demand.
The new repository wastes a lot of space. Why use big boxes when a list does a much better job?
Please show relevant information like number of downloads, last update...
A "list by" funct...First show an overview, then detail on demand.
The new repository wastes a lot of space. Why use big boxes when a list does a much better job?
Please show relevant information like number of downloads, last update...
A "list by" function would also be helpful: List by
- Number of downloads
- TYPO3 Version
- Relevance
Thank you for your work.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/196Layout suggestions2021-02-15T18:22:47ZpixeldesuLayout suggestionsThe entire layout and sizing of the website feels way too large. _(on screens that are not high resolution/retina)_
It fills the entire screen width for certain device widths (`.container-fluid`) and the headings chosen for the card-tit...The entire layout and sizing of the website feels way too large. _(on screens that are not high resolution/retina)_
It fills the entire screen width for certain device widths (`.container-fluid`) and the headings chosen for the card-titles are way too large as well, wasting a lot of screen space.
Here an example, for a _side-by-side_ view. This first screenshot is the current website as-is.
![Selection_262](/uploads/232478dbb288a2749ea0d86dadec084a/Selection_262.png)
And this is a locally modified version (with Chrome DevTools) just to narrow down a lot of things.
![Selection_263](/uploads/dd907cf63ab30d6e6c3c0b417a812cbf/Selection_263.png)
_(both screenshots capture exactly the same viewport, just from different tabs, no tricking with zoom-levels here :smile: )_
**What I changed:**
* Switched out the `.container-fluid` that a huge part of the site used, replaced it with just `.container` instead.
* Replaced all card headings with `h3` instead of `h2` and all subtitles with `h5` instead of `h4`
* _I also adjusted the padding of the TYPO3 logo, just to properly line up the navigation with the container_
These are not too significant changes to the site layout, but they already make a huge difference compared to what there was before.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/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/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/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.Backlog