extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2023-06-15T19:18:04Zhttps://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/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/519Show Distribution Image in List and Detail view2023-06-15T19:18:33ZStefan BusemannShow Distribution Image in List and Detail view### Problem to solve
As a user, I want to identify distributions, in the list and detail view
**Acceptence Criterias**
* [ ] List view shows an icon or the distribution image
* [x] detail view shows the distribution image
### Lin...### Problem to solve
As a user, I want to identify distributions, in the list and detail view
**Acceptence Criterias**
* [ ] List view shows an icon or the distribution image
* [x] detail view shows the distribution image
### Links / references_Ready for sprintThomas LöfflerThomas Löfflerhttps://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/513Sentry Client and Server for development and supervision2022-06-16T10:15:43ZStefan BusemannSentry Client and Server for development and supervisionAs the PO of the site, I want to ensure, that the site runs without any errors
AC:
* Sentry Server is added for local development
* Sentry client is added and
* configured for local development
* configured for production developmentAs the PO of the site, I want to ensure, that the site runs without any errors
AC:
* Sentry Server is added for local development
* Sentry client is added and
* configured for local development
* configured for production development_Ready for sprinthttps://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/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/501Extensions Stars - Github/Gitlab2022-06-16T10:15:44ZTomas Norre MikkelsenExtensions Stars - Github/Gitlab### Problem to solve
It's not a problem but an idea.
What about have the GitHub/Gitlab stars for a repository, reflected on the TER as well? This way we would easier get extensions "promoted" within the TER as well.### Problem to solve
It's not a problem but an idea.
What about have the GitHub/Gitlab stars for a repository, reflected on the TER as well? This way we would easier get extensions "promoted" within the TER as well._Ready for sprinthttps://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/482GDPR Admin function2022-06-16T10:15:45ZStefan BusemannGDPR Admin functionAs a TER admin I want to be able, to remove meta data of extensions.
UAC:
* Edit view of Extension offers the option to remove the author info
* List view displays "abandoned_extensions" as author
* Search function respects the changeAs a TER admin I want to be able, to remove meta data of extensions.
UAC:
* Edit view of Extension offers the option to remove the author info
* List view displays "abandoned_extensions" as author
* Search function respects the change_Ready for sprinthttps://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/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/417Ensure valid composer.json for extensions2022-04-04T17:31:03ZspetersEnsure valid composer.json for extensions### Problem to solve
* Some extensions do not include a composer.json.
* Some extensions do not have a valid composer.json or include a composer.json with deprecations.
* Information about composer.json (for extensions) is not consisten...### Problem to solve
* Some extensions do not include a composer.json.
* Some extensions do not have a valid composer.json or include a composer.json with deprecations.
* Information about composer.json (for extensions) is not consistent and not regularly updated.
To further propagate use of Composer and use of best practices for composer.json and to ensure stressless installation and
maintainance of TYPO3 sites, it might be useful to do some basic checks on extensions.
### Example
bp_pagetree
```
$ composer validate
```
```
Deprecation warning: replace.bp_pagetree is invalid, it should have a vendor name, a forward slash, and a package name. The vendor and package name can be words separated by -, . or _. The complete name should match "[a-z0-9]([_.-]?[a-z0-9]+)*/[a-z0-9]([_.-]?[a-z0-9]+)*". Make sure you fix this as Composer 2.0 will error.
```
```
composer --version
Composer version 1.9.1 2019-11-01 17:20:17
```
composer.json:
```
"replace": {
"bp_pagetree": "self.version",
"typo3-ter/bp_pagetree": "self.version"
},
```
See also:
* Issue about deprecations in composer.json of core extensions: https://forge.typo3.org/issues/89392
* The patch drops the replace section entirely: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61944
### Further details
long term goal:
* all TYPO3 extensions listed on extensions.typo3.org include valid composer.json
* documentation for extension authors is consistent and easily findable (beyond scope of this issue, should be handled in documentation)
### Proposal
Regularly run `composer validate` on extensions listed on extensions.typo3.org.
### What does success look like, and how can we measure that?
**Acceptence Criterias**
* [ ] Extension authors are regularly notified about problems (or possible improvements) with their extensions
* [ ] If problems are detected, the problems are listed for the extensions
* [ ] Best practices for composer.json are documented and regularly updated, e.g. on https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ExtensionArchitecture/ComposerJson/Index.html and in Installation & Upgrade Guide
### Related
* core issue: https://forge.typo3.org/issues/89392
* documentation issue: https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-CoreApi/issues/641
* documentation page for composer.json: https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ExtensionArchitecture/ComposerJson/Index.html_Ready for sprinthttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/401Adjust GitLab Issue Template Labels2022-04-04T17:34:23ZpixeldesuAdjust GitLab Issue Template LabelsJust as in #400, the GitLab Issue Template also requires adjustment of the proper group labels to be used. The GitLab issue templates are located in `.gitlab/issue-templates` in the projects root.
**Acceptance Criteria:**
* [ ] Issues ...Just as in #400, the GitLab Issue Template also requires adjustment of the proper group labels to be used. The GitLab issue templates are located in `.gitlab/issue-templates` in the projects root.
**Acceptance Criteria:**
* [ ] Issues created using GitLab issue templates in the extensions.typo3.org repository use the proper group labels_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 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/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/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/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.Backlog