extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2021-02-15T18:22:33Zhttps://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/296In Admin->Searchresult the header is missing2022-08-12T11:45:33ZStephan GroßberndtIn Admin->Searchresult the header is missingWhen searching for an extension key in "Managing my extensions" -> "Admin" on the result page the header "Managing my extensions" and the tabs to switch between "Managing extension keys", "Register extension key", "Transfer extension key...When searching for an extension key in "Managing my extensions" -> "Admin" on the result page the header "Managing my extensions" and the tabs to switch between "Managing extension keys", "Register extension key", "Transfer extension key", "Admin" are missing.
![Screenshot_2017-12-11_19.15.33](/uploads/67cbdca32474d95133ff8af0383d8aac/Screenshot_2017-12-11_19.15.33.png)_Ready for sprinthttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/300Trigger notification request to t3extensions.org2021-08-19T13:24:04ZMichael SchamsTrigger notification request to t3extensions.org_(as discussed with Thomas Löffler and Mathias Schreiber on Slack)_
# Real-time Notification of Extension Updates
## Feature Overview
This new feature triggers an HTTPS request to a specific API endpoint at [t3extensions.org](https://..._(as discussed with Thomas Löffler and Mathias Schreiber on Slack)_
# Real-time Notification of Extension Updates
## Feature Overview
This new feature triggers an HTTPS request to a specific API endpoint at [t3extensions.org](https://t3extensions.org), whenever a new extension version gets uploaded or a new extension published at the TER.
## Benefits
Currently, [t3extensions.org](https://t3extensions.org) features a Slash command for [typo3.slack.com](https://typo3.slack.com) to allow users to retrieve details of an extension (see typical use case below). The underlying NoSQL database gets updated a few times a day only, so the extension details are sometimes outdated.
By implementing the feature described below, we aim for a real-time update of the data, so Slack would always show accurate details of extensions.
## Use Case
In any channel (public or private) or direct message communication between users on [typo3.slack.com](https://typo3.slack.com), command `/extension <extension_key>` returns details about the extension with extension key equals `<extension_key>`. This has been implemented and is available and actually used already.
For example:
```
/extension powermail
```
Details such extension title, key, author, latest version, last update date, description, etc. is posted into the Slack channel, assuming the extension exists.
## Requirements
As soon as a new TYPO3 extension version gets uploaded to the TER, a **POST** request should be triggered to a specific API endpoint. The endpoint URL should be configurable. The payload (data in the body of the request) is a JSON object with the following keys/values.
```
{
"token": "<token>",
"source": "extensions.typo3.org",
"data": {
"extension_key": "<extension_key>",
"version": "<version>",
"integer_version": "<integer_version>",
"state": "<state>",
"title": "<title>",
"description": "<description>",
"author_name": "<author_name>",
"last_updated": "<timestamp>"
}
}
```
| Key: | Description: | Example: | Notes: |
| :------------------------- | :-------------------------------------- | :--------------------- | :----: |
| `token` | Access token | `AEEK4K2a8OgSRcXz` | (1) |
| `source` | Source identifier | `extensions.typo3.org` | (2) |
| `data` | _JSON object, see below_ | | |
| `data` → `extension_key` | Extension key | `powermail` | |
| `data` → `version` | Extension version (format: X.Y.Z) | `1.2.3` | |
| `data` → `integer_version` | Extension integer version | `1002003` | |
| `data` → `state` | Extension state (arbitrary text) | `beta` | |
| `data` → `title` | Extension title (arbitrary text) | `Powermail` | |
| `data` → `description` | Extension description (arbitrary text) | `Lorem ipsum...` | |
| `data` → `author_name` | Extension author (arbitrary text) | `Brad Pitt` | |
| `data` → `last_updated` | UNIX timestamp of last update in UTC | `1514524068` | |
### Notes
(1) The _access token_ should be configurable. The token must be classified as sensitive information and is therefore not included in this publicly accessible feature request. Please contact me on Slack: https://typo3.slack.com/messages/D1KECK1EF
(2) The _source_ identifies, which service or server initiates the request. Useful for debugging purposes at [t3extensions.org](https://t3extensions.org). In case the TER runs in a distributed server setup, the host name can be used as the _source_. Otherwise, `extensions.typo3.org` could be a good value.
### API Endpoint URLs
#### Method: **Update Extension**
A `POST` request to `https://slack.t3extensions.org/v1/UpdateExtension` updates the details of a specific extension. This request requires a valid _token_ and further data (see details above) as the payload.
The API method automatically detects, if the details of an existing extension need to be updated or if the request is for a new extension (first version of an extension). The `<extension_key>` is used as the identifier.
#### Method: **Show Test Table**
The `UpdateExtension` API method uses a **test database table** during development. To retrieve the data of this test table, a `GET` request to `https://slack.t3extensions.org/v1/ShowTestTable` can be executed.
## API Tests
### Update Extension Details on Command Line
```
# DATA='{"token": "secret-token", "source": "testing", "data": {"extension_key": "myextension", "version": "1.2.3", "integer_version": "1002003", "state": "alpha", "title": "My Test Extension", "description": "This is just a test entry for t3extensions.org", "author_name": "Johnny Depp", "last_updated": "1512270379"}}'
# curl -s -X POST --data "${DATA}" -H "Content-Type: application/json" https://slack.t3extensions.org/v1/UpdateExtension
```
### Retrieve Data from Test Table on Command Line
```
# curl -s https://slack.t3extensions.org/v1/ShowTestTable
```
The content of the test table can also be access in a standard browser of course: https://slack.t3extensions.org/v1/ShowTestTable
## Error Handling
If the data update fails, the API method returns a JSON object with an error description. For example:
```
{
"result": "failed",
"request_id": "4083432a-ec5c-11e7-bed9-f33584834239",
"response": [
{
"message": "Security token mismatch",
"code": 102
}
]
}
```
## Restrictions
The code at [t3extensions.org](https://t3extensions.org) uses a cloud-based, serverless microservice at [Amazon Web Services](https://aws.amazon.com).
In order to control resources and costs, the number of read/write operations to the NoSQL database and the CPU and memory consumption of the API methods are limited intentionally. Too many requests within a certain time frame may result in an error message.
Version 1 of API method `UpdateExtension` currently supports **one** update request only. As a logical consequence, each extension update requires a notification request to the API method. The update of multiple extensions in one request is not supported at this point in time._Ready for sprinthttps://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/320Extension key registration - rules for underscores not applied2022-04-04T17:31:01ZDan Kleine (geb. Dan Untenzu)Extension key registration - rules for underscores not applied## What was the cause of the issue?
*Register extension key*
> An extension key must have minimum 3, maximum 30 characters (not counting underscores).
This rules implies, that any number of underscores is allowed.
However the form a...## What was the cause of the issue?
*Register extension key*
> An extension key must have minimum 3, maximum 30 characters (not counting underscores).
This rules implies, that any number of underscores is allowed.
However the form actually does count underscores.
## Steps to reproduce
Registering `test_______________________test` (31 characters) is not possible (but should), registering `test______________________test` (30 characters) is possible. Registering `aa` is not possible, registering `a_a` is possible (but should'nt).
long
![Bildschirmfoto_vom_2018-02-22_15-04-45](/uploads/7e7898c46d1a60988753189a2eb21083/Bildschirmfoto_vom_2018-02-22_15-04-45.png)
short
![Bildschirmfoto_vom_2018-02-22_15-11-19](/uploads/af2abadb85c2b4d1e6b0fa71f754ee64/Bildschirmfoto_vom_2018-02-22_15-11-19.png)
## Possible solution
* Either remove the “(not counting underscores)” rule
* …or fix the validation to follow the given rule_Ready for sprinthttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/321Increase max character length for extension key2022-04-04T17:31:04ZDan Kleine (geb. Dan Untenzu)Increase max character length for extension key## What kind of feature do you want?
*Register extension key*
> An extension key must have minimum 3, maximum 30 characters (not counting underscores).
Where does the maximum value origin, and is it possible to increase it? Since exte...## What kind of feature do you want?
*Register extension key*
> An extension key must have minimum 3, maximum 30 characters (not counting underscores).
Where does the maximum value origin, and is it possible to increase it? Since extension developers are urged to use speaking variables and not come up with odd abbreviations the 30 character limit is obstructive.
## What are the benefits?
* Speaking extension names
* Less odd abbreviations just to fit the character max size
* Same names on Github and Packagist possible (instead of shortcuts to fit the TER naming rules)
* Eason forks/patch extensions (»acme_extension_with_long_name« → »acme_extension_with_long_name_patched« instead of »acme_extension_with_l_patched«)
## Add some use case
Github allows repository names with a maximum of 100 characters. I often need more than 30 characters and would like to use the same key as GitHub repo name, TYPO3 extension key, Composer package name etc._Ready for sprinthttps://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/382Add information about publishing an extension to FAQ2022-06-16T10:18:14ZspetersAdd information about publishing an extension to FAQThere is a page: https://extensions.typo3.org/faq/publish-an-extension/
Can you add an item and link to that page to the [FAQ](https://extensions.typo3.org/faq/) list (preferably at the top)?
It is available in the menu on the top, but...There is a page: https://extensions.typo3.org/faq/publish-an-extension/
Can you add an item and link to that page to the [FAQ](https://extensions.typo3.org/faq/) list (preferably at the top)?
It is available in the menu on the top, but that is not the first place I would look.
Also, there is general information about publishing extensions in TYPO3 Explained: https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ExtensionArchitecture/PublishExtension/Index.html_Ready for sprinthttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/385Suggestion: Add core extensions to extension directory2022-04-04T17:34:25ZspetersSuggestion: Add core extensions to extension directory### Problem to solve
* confusion about where to find things
### Further details
Some things have changed: You used to install the core and then you had the extension manager and TER to install additional third party extensions.
Now,...### Problem to solve
* confusion about where to find things
### Further details
Some things have changed: You used to install the core and then you had the extension manager and TER to install additional third party extensions.
Now, since the **subtree split** it is not so different for the end user to install additional core components (system extensions) or third party extensions.
### Proposal
If extensions.typo3.org is nowadays rather used as a catalog (if I understand it correctly), it might be useful to show all, not just the third party extensions.
Of course, the core extensions should be marked as part of the core to underline that they are supported officially by TYPO3.
### What does success look like, and how can we measure that?
* (almost?) all system extensions are searchable in extension directory
* system extensions are clearly marked as system extensions
* if third party extensions depends on system extension, a link is used to link to the sysext in "Dependencies" section
* the composer command is listed for the system extension
## Advantages:
* find everything in one place
* easily find Composer command (or package name) for installing a core extension without having to go to packagist
* dependencies to sysexts could be added as links, e.g. see [rte_ckeditor_image](https://extensions.typo3.org/extension/rte_ckeditor_image/) (depends on rte_ckeditor, this could be a link, as in ext:introduction -> ext:bootstrap_package)
![rte_ckeditor_image](/uploads/b891004c1f19388a8d6fa5b273316495/rte_ckeditor_image.png)
![introduction](/uploads/5f29c3dcb1635b9cb212e2be455db105/introduction.png)
For me, the question is: What is useful for the end user?_Ready for sprinthttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/396Update information about extension documentation in FAQ2022-04-04T17:31:43ZspetersUpdate information about extension documentation in FAQThese 2 documentation related things are outdated:
> Although I uploaded a manual, it is not displayed at docs.typo3.org - why?
> I have problems with the reST format to document my extension - where can I get help?
**In general, it w...These 2 documentation related things are outdated:
> Although I uploaded a manual, it is not displayed at docs.typo3.org - why?
> I have problems with the reST format to document my extension - where can I get help?
**In general, it would be good to point people to docs.typo3.org, so we can keep this information updated ourselves. Just let us know, what is missing.**
outdated:
1. ~~In addition you can use the extension sphinx to proof if everything is fine on your local system~~
Using the Docker image for local rendering is the recommended method. See
https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/RenderingDocs/Index.html
Additionally, you can create a documentation-draft
branch which will automatically be rendered as draft (not indexed by search engines).
2. ~~That is ./Documentation/Index.rst or ./README.rst.~~
Can also be any of: https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/GeneralConventions/DirectoryFilenames.html#supported-filenames-and-formats
3. ~~Rendering takes time. The documentation is fetched cyclically by docs server~~
No longer true. Rendering is triggered by Webhook.
4. ~~To get an introduction to reStructuredText take the sphinx extension as an example. Further more the format is well
documented at sphinx-doc.org/rest.html. In addition the documentation of the sphinx extension has further information.~~
Best to point people to our official docs: https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/WritingReST/Index.html
5. ~~On the page https://docs.typo3.org/Extensions/ you get a list of tools and worflows how to best document your extension in reST.~~
This page no longer exists (404). I don't know what used to be on there. I think it is best to point them to https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/WritingReST/Index.html# for general information about reST and to https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/WritingDocForExtension/Index.html for extension documentation._Ready for sprinthttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/400Switch extensions.typo3.org Feedback Form GitLab Labels2022-04-04T17:34:23ZpixeldesuSwitch extensions.typo3.org Feedback Form GitLab Labels### Problem to solve
At the typo3.org DevDays 2019 Sprint we adjusted GitLab labels to a more uniform format, also planning to focus more on group labels for better sorting. The feedback forms have their own project-specific set of labe...### Problem to solve
At the typo3.org DevDays 2019 Sprint we adjusted GitLab labels to a more uniform format, also planning to focus more on group labels for better sorting. The feedback forms have their own project-specific set of labels which we should switch away from to have as few project-specific labels as possible.
### Further details
The Feedback form configuration for extensions.typo3.org includes a set of labels and a configurable label for each feedback type selection.
### Proposal
Adjust the existing labels in the feedback form configuration to reflect the group labels from the t3o group! https://git-t3o.typo3.org/groups/t3o/-/labels
### What does success look like, and how can we measure that?
The issues created from the extensions.typo3.org feedback form use t3o group labels instead of project labels from the typo3.org repository
**Acceptence Criterias**
* [ ] Change the labels from the Feedback form to use t3o group labels (by name)
* [ ] Remove the site specific "extensions.typo3.org" label, as the issue gets created in the typo3.org repository already_Ready for sprint