extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2021-01-14T12:00:56Zhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/502Extension "Last Update" is not updated correctly when using the REST API2021-01-14T12:00:56ZChristian BuelterExtension "Last Update" is not updated correctly when using the REST APIThe Date "Last update" is not updated correctly when an extension is uploaded via tailor / REST API.
That leads also to the extension not beeing shown in the list of newest extensions (initial view on extensions.typo3.org).
see Screens...The Date "Last update" is not updated correctly when an extension is uploaded via tailor / REST API.
That leads also to the extension not beeing shown in the list of newest extensions (initial view on extensions.typo3.org).
see Screenshot
![Auswahl_154](/uploads/a9a1d028e15341f434ded2d53c16c7f5/Auswahl_154.png)Oliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/497Packagist stats not displayed in "Downloads by month"2020-12-15T14:29:28ZChris MüllerPackagist stats not displayed in "Downloads by month"### Summary
The downloads statistics for packagist are not displayed for some extensions.
### Example URL
https://extensions.typo3.org/extension/schema/
### What is the current *bug* behavior?
Only TER and extension manager download...### Summary
The downloads statistics for packagist are not displayed for some extensions.
### Example URL
https://extensions.typo3.org/extension/schema/
### What is the current *bug* behavior?
Only TER and extension manager downloads are displayed.
### What is the expected *correct* behavior?
**Acceptence Criterias**
* [ ] The statistics for packagist are displayed as well.
### Possible fixes
Seems it occurs because my version tags start "v", e.g. "v1.9.0".Tomas Norre MikkelsenTomas Norre Mikkelsenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/496I can't create an access token for one extension only2020-12-03T08:05:19ZThomas LöfflerI can't create an access token for one extension onlyReproduce:
1. Head to "My access token" on extensions.typo3.org
1. Create a token and select one extension
1. Result:
![Bildschirmfoto_2020-12-02_um_18.38.42](/uploads/7e0ff2c3cec3483d8ee299551d606207/Bildschirmfoto_2020-12-02_um_18.38...Reproduce:
1. Head to "My access token" on extensions.typo3.org
1. Create a token and select one extension
1. Result:
![Bildschirmfoto_2020-12-02_um_18.38.42](/uploads/7e0ff2c3cec3483d8ee299551d606207/Bildschirmfoto_2020-12-02_um_18.38.42.png)Oliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/494Soften extension key pattern in TokenCreationValidator2020-11-27T11:37:08ZOliver BartschSoften extension key pattern in TokenCreationValidatorCurrently the validator uses the strict patter `/^((?!(tx|user|pages|tt|sys|ts_language|csh))[a-z]{1}[a-z0-9_]+)$/` which is used for creating new extension keys. However, since there are already extensions (like `tt_address`) which do n...Currently the validator uses the strict patter `/^((?!(tx|user|pages|tt|sys|ts_language|csh))[a-z]{1}[a-z0-9_]+)$/` which is used for creating new extension keys. However, since there are already extensions (like `tt_address`) which do not follow this pattern, this must be replaced with a less strict one (something like `/^[a-z][a-z0-9_]{2,29}$/`). Otherwise access tokens can not be restricted to such extension keys.
As a side task, the pattern used in the OpenAPI specification for the `key` parameter should also be changed to this pattern since it currently contains a meaningless quantifier.Oliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/493Add more documentation to the API2020-11-27T09:10:46ZOliver BartschAdd more documentation to the APIOliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/492Add logging and support for multiple authorization fields2020-11-26T19:29:27ZOliver BartschAdd logging and support for multiple authorization fieldsOliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/490Add composer script to run php-cs-fixer locally2020-11-26T19:13:10ZOliver BartschAdd composer script to run php-cs-fixer locallyTo prevent failing pipelines, it should be possible to run the `php-cs-fixer` locally before committing changes.To prevent failing pipelines, it should be possible to run the `php-cs-fixer` locally before committing changes.Oliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/488TER Upload: SOAP Error "not found"2020-11-06T14:12:32ZMarcus SchwemerTER Upload: SOAP Error "not found"I am trying to upload an extension release to extensions.TYPO3.org via a soap client.
So far I used `helhum/ter-client` and `namelesscoder/typo3-repository-client`.
`namelesscoder/typo3-repository-client` uses http://typo3.org/wsdl/tx_...I am trying to upload an extension release to extensions.TYPO3.org via a soap client.
So far I used `helhum/ter-client` and `namelesscoder/typo3-repository-client`.
`namelesscoder/typo3-repository-client` uses http://typo3.org/wsdl/tx_ter_wsdl.php as `WSDL_URL`. \
`helhum/ter-client` uses https://extensions.typo3.org/wsdl/tx_ter_wsdl.php as `WSDL_URL`
Both fail with the message "Not found". See "Actions" on
* typo3_repository_client: https://github.com/in2code-de/groupdelegation/runs/1363237475?check_suite_focus=true
* ter-client: https://github.com/in2code-de/groupdelegation/runs/1363139391?check_suite_focus=true
Something changed here?Marcus SchwemerMarcus Schwemerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/480Improved page title on extension detail page2020-10-25T07:58:44ZGeorg RingerImproved page title on extension detail page### Problem to solve
The page title on a extension's detail page is currently rather poor.
### Further details
E.g. on https://extensions.typo3.org/extension/news/ it is `News system`.
### Proposal
I would suggest a page title `TYPO...### Problem to solve
The page title on a extension's detail page is currently rather poor.
### Further details
E.g. on https://extensions.typo3.org/extension/news/ it is `News system`.
### Proposal
I would suggest a page title `TYPO3 Extension 'News system' (news)`https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/473DDEV post-import-db hook fails with "The --username option does not exist."2020-09-15T09:48:18ZOliver BartschDDEV post-import-db hook fails with "The --username option does not exist."### Summary
The `post-import-db` hook in the default ddev configuration calls the `backend:createadmin` command using `username` and `password` as option. These parameters however are registered as `arguments`.
### Steps to reproduce
...### Summary
The `post-import-db` hook in the default ddev configuration calls the `backend:createadmin` command using `username` and `password` as option. These parameters however are registered as `arguments`.
### Steps to reproduce
Run `ddev import-db --src=%source%`
### What is the current *bug* behavior?
Error on execution
### What is the expected *correct* behavior?
Backend user gets created without further errors
### Possible fixes
The correct hook therefore would be:
```
- exec: vendor/bin/typo3cms backend:createadmin admin password
```Oliver BartschOliver Bartschhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/472Can not access my own extension list2020-09-09T09:37:07ZStefan FroemkenCan not access my own extension list### Summary
I can not access my extension list
### Steps to reproduce
Just login. There is no link to your extension list.
### Example URL
https://extensions.typo3.org/
### What is the current *bug* behavior?
I can not find a link...### Summary
I can not access my extension list
### Steps to reproduce
Just login. There is no link to your extension list.
### Example URL
https://extensions.typo3.org/
### What is the current *bug* behavior?
I can not find a link to my extension list
### What is the expected *correct* behavior?
In earlier versions there was a "My Extensions" link just behind the "FAQ"-Link
### Relevant logs and/or screenshots
![Bildschirmfoto_2020-09-09_um_11.14.45](/uploads/69f5afb9168aa92d9c1a74a261afad29/Bildschirmfoto_2020-09-09_um_11.14.45.png)
### Possible fixes
Reload the page after loginStefan FroemkenStefan Froemkenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/471Upload fails: Wrong parameters for T3o\Ter\Exception\UnauthorizedException2020-09-09T08:53:10ZMathias BrodalaUpload fails: Wrong parameters for T3o\Ter\Exception\UnauthorizedException<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label.
For Layout issues please use this tracker:
- https://git-t3o.typo3.org/t3o/t3olayout/issues?label_name%5B%...<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label.
For Layout issues please use this tracker:
- https://git-t3o.typo3.org/t3o/t3olayout/issues?label_name%5B%5D=bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Uploading an extension to TER using [helhum/ter-client](https://packagist.org/packages/helhum/ter-client) fails with an error which indicates an issue on the TER side.
### Steps to reproduce
Try to upload an extension using the helhum/ter-client.
### What is the current *bug* behavior?
I get an error which can only come from TER since the mentioned class does only exist in the code of the TER:
`Wrong parameters for T3o\Ter\Exception\UnauthorizedException`
### What is the expected *correct* behavior?
The extension should be uploaded successfully.
**Acceptence Criterias**
* [ ] Must be fullfilled
### Relevant logs and/or screenshots
```
$ composer global exec -v -- ter-client upload --username $TYPO3_ORG_USERNAME --password $TYPO3_ORG_PASSWORD --upload-comment "$(git tag -l --format='%(contents)' $TRAVIS_TAG)" $(composer config extra.typo3/cms.extension-key) .
Changed current directory to /home/docker/.composer
> __exec_command: ter-client 'upload' '--username' '<username>' '--password' '<password>' '--upload-comment' '<upload-comment>' '<extension-key>' '.'
In Connection.php line 52:
Wrong parameters for T3o\Ter\Exception\UnauthorizedException([string $messa
ge [, long $code [, Throwable $previous = NULL]]])
upload [-u|--username [USERNAME]] [-p|--password [PASSWORD]] [-m|--upload-comment [UPLOAD-COMMENT]] [--wsd-url [WSD-URL]] [--] <extensionKey> <directory>
Script ter-client handling the __exec_command event returned with error code 1
```
### Possible fixes
I checked the TER code but cannot find a possible cause in the current code base. I am not sure if this reflects the latest deployed state though.
### Cross-link
Issue for helhum/ter-client: https://github.com/helhum/ter-client/issues/12Mathias BrodalaMathias Brodalahttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/466Follow-up from "[TASK] Use Environment API instead of PATH_site"2020-08-07T16:42:45ZThomas LöfflerFollow-up from "[TASK] Use Environment API instead of PATH_site"The following discussion from !557 should be addressed:
- [ ] @tomalo.stuttgart started a [discussion](https://gitlab.typo3.org/t3o/ter/-/merge_requests/557#note_25540): (+2 comments)
> ```suggestion:-0+0
> General...The following discussion from !557 should be addressed:
- [ ] @tomalo.stuttgart started a [discussion](https://gitlab.typo3.org/t3o/ter/-/merge_requests/557#note_25540): (+2 comments)
> ```suggestion:-0+0
> GeneralUtility::getURL(Environment::getPublicPath() . '/' . $GLOBALS['TYPO3_CONF_VARS']['BE']['fileadminDir'] . 'currentcoredata.json'),
> ```Tomas Norre MikkelsenBenni MackTomas Norre Mikkelsenhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/459Register extension key leads to error2020-07-21T07:26:11ZNikita HovratovRegister extension key leads to errorTyping in a valid extension key and pressing "Register" in https://extensions.typo3.org/my-extensions/ lead to oops error.Typing in a valid extension key and pressing "Register" in https://extensions.typo3.org/my-extensions/ lead to oops error.Benni MackBenni Mackhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/458TER - Keeping expiring extensions ends in "Oops, an error occurred!"2020-07-16T11:02:54ZDaniel HettlerTER - Keeping expiring extensions ends in "Oops, an error occurred!"
### Summary
I try to keep one of my expiring extension keys in the TER. I click on the button "keep" but the action ends in "Oops, an error occurred!
### Steps to reproduce
Go to the expiring keys section at https://extensions.typo3....
### Summary
I try to keep one of my expiring extension keys in the TER. I click on the button "keep" but the action ends in "Oops, an error occurred!
### Steps to reproduce
Go to the expiring keys section at https://extensions.typo3.org/my-extensions/
This call breaks: https://extensions.typo3.org/my-extensions/?tx_terfe2_pi1%5Baction%5D=keep&tx_terfe2_pi1%5Bcontroller%5D=Registerkey&tx_terfe2_pi1%5Bextension%5D=18844&cHash=89acf1bbac0143e76a...
### What is the expected *correct* behavior?
I should be able to keep my extension keys when they are about to expire.Daniel HettlerDaniel Hettlerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/457Zipped extension misses files with no content2020-07-16T10:44:44ZThomas LöfflerZipped extension misses files with no contentThomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/454Migrate tx_ter_extensionqueue to TER v22020-07-08T14:03:14ZBenni MackMigrate tx_ter_extensionqueue to TER v2The table tx_ter_extensionqueue has a TCA which is completely unneeded.
In addition, it is only used in two places, in the SOAP API (when an extension has been uploaded) and in a scheduler task to process an uploaded extension.
I sugge...The table tx_ter_extensionqueue has a TCA which is completely unneeded.
In addition, it is only used in two places, in the SOAP API (when an extension has been uploaded) and in a scheduler task to process an uploaded extension.
I suggest to:
* Remove the TCA definition and only keep this is as a DB table with necessary fields (uid, createdon=timestamp, extensionkey, extensiondetailsid, processedon=timestamp or null)
* We then do not put this into a Repository class in EXT:terfe2, but like a QueueProcessingStack class with a "->getNextQueueItem()" and a "->markAsProcessed()" and direct Doctrine DBAL queries. We then change the code within tx_ter_api to just use the new API and make tx_ter a bit smaller again.https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/447Oops an error occurred while registering a new ExtKey2020-04-14T08:24:50ZStefan FroemkenOops an error occurred while registering a new ExtKeyIt seems that the ExtKey was registered, but it is not connected with my account and I can not re-register this ExtKey.
Can you please assign sfmailshop to my Account: froemken
Thank you
StefanIt seems that the ExtKey was registered, but it is not connected with my account and I can not re-register this ExtKey.
Can you please assign sfmailshop to my Account: froemken
Thank you
Stefanhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/403Unable to edit extension settings in my-extensions after upload of the first ...2019-08-07T11:26:42ZJo HasenauUnable to edit extension settings in my-extensions after upload of the first versionAfter the first upload of the Localizer extension it's not possible anymore to edit the extension settings in the "My extensions" list on extensions.typo3.org
While any other extension belonging to the user "Coders-Care" can be edited, ...After the first upload of the Localizer extension it's not possible anymore to edit the extension settings in the "My extensions" list on extensions.typo3.org
While any other extension belonging to the user "Coders-Care" can be edited, the Localizer fails with the message: You must be the owner of the extension to edit it.
Is it possible to change that on the server side or de we have to change the owner of the extension in ext_emconf.php and/or composer.json?https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/389Improve signup form2019-04-17T10:51:12ZGeorg RingerImprove signup formI just registered a new user and there are 2 things which could be improved:
- HTML5 validation would reduce load and improve UX
- I got the error "Username: Username is blocked." and this is not understable. what does this mean?I just registered a new user and there are 2 things which could be improved:
- HTML5 validation would reduce load and improve UX
- I got the error "Username: Username is blocked." and this is not understable. what does this mean?