extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2021-02-15T18:22:32Zhttps://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 expiredBacklog