extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2022-04-04T17:06:49Zhttps://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/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/219no_cache parameter breaks the detailview (random parameter as well)2019-11-28T16:00:52ZNadir S.no_cache parameter breaks the detailview (random parameter as well)if you add no_cache parameter to a detailview, the page output is not correctly displayed anymore
https://extensions.typo3.org/extension/wfqbe/?no_cache=1
not just no_cache..
https://extensions.typo3.org/extension/wfqbe/?foobar=1 brea...if you add no_cache parameter to a detailview, the page output is not correctly displayed anymore
https://extensions.typo3.org/extension/wfqbe/?no_cache=1
not just no_cache..
https://extensions.typo3.org/extension/wfqbe/?foobar=1 breaks the view as well.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/181Let the counter chart stack download channels2021-02-15T18:22:50ZThomas MayerLet the counter chart stack download channelsFollowing up to #179:
## What kind of feature do you want?
Download counts for each channel (Packagist-composer, TER-composer, TER-EM, TER-manual-download) could be stacked upon each other in the chart.
I suggest to use a single bar f...Following up to #179:
## What kind of feature do you want?
Download counts for each channel (Packagist-composer, TER-composer, TER-EM, TER-manual-download) could be stacked upon each other in the chart.
I suggest to use a single bar for each version whereas the portion of each channel gets a different color. Now that the channels are stacked on each other the totals are still visible (overall, that's still the most valuable information).
Now that highcharts supports stacking, it should still be of use.
## What are the benefits?
We would see which download channel is used by users.
## Alternative
Highcharts also supports line charts (with colored areas) which can be stacked.Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/179Integrate composer2022-04-04T17:34:25ZThomas LöfflerIntegrate composer* Read out composer.json if existing
* Show `composer require` command with package name
* Get download counter from packagist and add it to TER downloads
Relates: #155 #164* Read out composer.json if existing
* Show `composer require` command with package name
* Get download counter from packagist and add it to TER downloads
Relates: #155 #164Backloghttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/169Important links should be more visible2020-09-12T13:54:22ZJérémie RoulinImportant links should be more visible## What do you suggest?
The "Extension Manual" link should be more visible. The external repository link should also be more visible. For me it should be placed next to download button. I would do something like that :
![Untitled](/up...## What do you suggest?
The "Extension Manual" link should be more visible. The external repository link should also be more visible. For me it should be placed next to download button. I would do something like that :
![Untitled](/uploads/186e4de92e027299937de6dee34b02a1/Untitled.png)
## Why?
The important links have to be accessible quickly.Backlog