extensions.typo3.org issueshttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues2018-03-31T11:41:52Zhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/340Give more info on extension when abandoned2018-03-31T11:41:52ZThomas LöfflerGive more info on extension when abandonedYou can't see any hints on detail page if an extension was abandoned. The former author is still displayed.
Example: https://extensions.typo3.org/extension/dwflickrgallery/You can't see any hints on detail page if an extension was abandoned. The former author is still displayed.
Example: https://extensions.typo3.org/extension/dwflickrgallery/Sprint 2018-03 (Release)Thomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/339Clean up editing extension2018-03-31T12:03:43ZThomas LöfflerClean up editing extension* Change label for link to issue tracker* Change label for link to issue trackerSprint 2018-03 (Release)Thomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/338Remove flattr integration2018-03-31T12:03:43ZThomas LöfflerRemove flattr integrationSprint 2018-03 (Release)Thomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/336Make feedback button less obstrusive2018-04-09T09:17:06ZFeedback from WebsiteMake feedback button less obstrusive[Mathias Brodala](mailto:mbrodala@pagemachine.de) reported an issue
The feedback button and especially the feedback bar at the bottom take a considerable amount of space from the extension repository view. Please consider making the but...[Mathias Brodala](mailto:mbrodala@pagemachine.de) reported an issue
The feedback button and especially the feedback bar at the bottom take a considerable amount of space from the extension repository view. Please consider making the button less obstrusive.
Reported URL:https://extensions.typo3.org/
User Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36Sprint 2018-03 (Release)https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/332Extension key transfer procedure in FAQ is incorrect2018-04-15T15:52:47ZFeedback from WebsiteExtension key transfer procedure in FAQ is incorrect[Jigal van Hemert](mailto:jigal.van.hemert@typo3.org) reported an issue
The procedure is described at https://forge.typo3.org/projects/team-ect/wiki/Extension_Key_Transfer
With the future removal of the mailing lists/forum/newsgroups th...[Jigal van Hemert](mailto:jigal.van.hemert@typo3.org) reported an issue
The procedure is described at https://forge.typo3.org/projects/team-ect/wiki/Extension_Key_Transfer
With the future removal of the mailing lists/forum/newsgroups the contact methods need to be revised (forge issues, slack channel, new discussion platform)
Reported URL:https://extensions.typo3.org/faq/
User Agent:Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0Sprint 2018-03 (Release)Stefan BusemannStefan Busemannhttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/329Make the link to contact an extension maintainer more prominent2018-03-31T11:41:52ZThomas LöfflerMake the link to contact an extension maintainer more prominent## What kind of feature do you want?
A linked button to the issue tracker instead of a nearly unvisible link in the info box
## What are the benefits?
Usability will be improved
## Add some use case## What kind of feature do you want?
A linked button to the issue tracker instead of a nearly unvisible link in the info box
## What are the benefits?
Usability will be improved
## Add some use caseSprint 2018-03 (Release)https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/324Link in the "Has manual"2018-04-09T09:16:22ZFeedback from WebsiteLink in the "Has manual"[Karavas](mailto:aristeidis.karavas@outlook.com) reported an issue
On the list view of the Extension Repository, there is the indication that the extension has a manual. I would love to see a link that goes straight to the manual.
Best...[Karavas](mailto:aristeidis.karavas@outlook.com) reported an issue
On the list view of the Extension Repository, there is the indication that the extension has a manual. I would love to see a link that goes straight to the manual.
Best regards
Reported URL:https://extensions.typo3.org/
User Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36Sprint 2018-03 (Release)https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/322Missing gap for cards on small screens2018-04-09T09:16:47ZPatrick LenkMissing gap for cards on small screensOn screens bigger than 992px the grid-gap for the result-list are 30px.
**On screens smaller than 992px each card sticks to the other and that looks weird.**
![list_current](/uploads/1dbae473ccbd975e5da84e9206a855c6/list_current.png)
...On screens bigger than 992px the grid-gap for the result-list are 30px.
**On screens smaller than 992px each card sticks to the other and that looks weird.**
![list_current](/uploads/1dbae473ccbd975e5da84e9206a855c6/list_current.png)
**A gap between the cards would enhance the UI of the list view on small screens.**
![list_should](/uploads/67699bdb924e82f3b4e06e07be0e9236/list_should.png)Sprint 2018-03 (Release)https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/319Change Piwik integration2018-03-08T16:33:36ZStefan BusemannChange Piwik integrationThe piwik code remains not longer in t3olayout. Please add the site code to the local configuration.
Todos:
* [x] Integrate in TS template
* [x] add correct siteId
`
<!-- Piwik -->
<script type="text/javascript">
var _paq = _paq || ...The piwik code remains not longer in t3olayout. Please add the site code to the local configuration.
Todos:
* [x] Integrate in TS template
* [x] add correct siteId
`
<!-- Piwik -->
<script type="text/javascript">
var _paq = _paq || [];
/* tracker methods like "setCustomDimension" should be called before "trackPageView" */
_paq.push(['trackPageView']);
_paq.push(['enableLinkTracking']);
_paq.push(['setVisitorCookieTimeout', '2592000']);
_paq.push(['setSessionCookieTimeout', '0']);
_paq.push(['setDoNotTrack', true]);
(function() {
var u="//piwik.typo3.org/";
_paq.push(['setTrackerUrl', u+'piwik.php']);
_paq.push(['setSiteId', '39']);
var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'piwik.js'; s.parentNode.insertBefore(g,s);
})();
</script>
`Sprint 2018-03 (Release)https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/276Create one time scheduler for salvage all extension keys2018-04-09T09:20:04ZStefan BusemannCreate one time scheduler for salvage all extension keysGoal:
We want to get rid of the old database structure, to have clean data.
Task
* [x] Create scheduler task to salvage all old extension keys
* [x] Remove salvage function in "Manage extension keys"
from https://forge.typo3.org/issu...Goal:
We want to get rid of the old database structure, to have clean data.
Task
* [x] Create scheduler task to salvage all old extension keys
* [x] Remove salvage function in "Manage extension keys"
from https://forge.typo3.org/issues/78667Sprint 2018-03 (Release)https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/229Extract distribution image to publicly available location2018-03-16T11:47:25ZAndreas KienastExtract distribution image to publicly available location## What kind of feature do you want?
I'd like to have the distribution image (Distribution.png/Distribution.svg) somewhere publicly available. A REST call to fetch the correct image automatically would be cherries on top :)
## What are ...## What kind of feature do you want?
I'd like to have the distribution image (Distribution.png/Distribution.svg) somewhere publicly available. A REST call to fetch the correct image automatically would be cherries on top :)
## What are the benefits?
The extension manager's distribution list is only able to show the distrbution image if the distribution is actually installed. With this feature, the image can be shown even if the distribution is not installed.Sprint 2018-03 (Release)Andreas KienastAndreas Kienasthttps://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/issues/180Let TYPO3 CMS releases go green if supported by ANY version of the extension2018-04-09T09:19:47ZThomas MayerLet TYPO3 CMS releases go green if supported by ANY version of the extension## What do you suggest?
In [search results](https://extensions.typo3.org/?L=0&id=1&tx_solr%5Bq%5D=seo), a TYPO3 CMS release turns green if it is supported by the *latest* version of an extension.
![Auswahl_352](/uploads/90f329dbffee2c9...## What do you suggest?
In [search results](https://extensions.typo3.org/?L=0&id=1&tx_solr%5Bq%5D=seo), a TYPO3 CMS release turns green if it is supported by the *latest* version of an extension.
![Auswahl_352](/uploads/90f329dbffee2c909b4fc2dd3ee38ec7/Auswahl_352.png)
![Auswahl_359](/uploads/5e9c9ff6ec0be0ebcddd9957f9ab1d72/Auswahl_359.png)
Instead, releases of TYPO3 CMS should go green if supported by *any* release of an extension
## Why?
If older releases of TYPO3 CMS are supported by *older* versions of an extension, there is no distinction to an extension which *never* supported a TYPO3 CMS release. Either the user gets confused for no reason or the user has to request every TER detail page for every entry shown in the search result to see if an old release of TYPO3 has ever been supported or not.
## Add a use case
Use case: For metaseo, we have
- metaseo 3.0.0 for TYPO3 CMS 8 LTS
- metaseo 2.1.0 for TYPO3 CMS 6.2 LTS - 7 LTS
We're maintaining a separate branch for 3.0.0, just because it was more or less painful to support 6.2 and 8 LTS in one version of the extension. And because we still need to support PHP 5.x for 7.6 and did not want to stuck with PHP 5.x (and even 5.3 for 6.2) for another 3 years.
Especially for the search it would be great to let any release of TYPO3 go green if only it was supported by *any* version of the extension. IMO, there is no practical use to show up the latest version number anyways because it's more or less meaningless to a user who searches for a new extension (number of downloads in past 12 months would be a much better metric).
## Implication
This issue implies that the search result should not be version specific. I also see no reason to have the search results to be specific to a particular version because
- Version information is meaningless to a user searching for a new extension (which I assume is the purpose of the search page)
- The download link itself is also available in the detail TER page. That's one click away and goes along with the user's working process to first decide which extension to use and then decide which version applies (eventually beneficial when using an older release of TYPO3).
- Do users still *use* the manual download feature (...for serious stuff) now that we have composer and also still have EM's own software distribution without manual download?
Plus, would it free up some space when the download link gets removed in search results. It could be used to display more entries and avoid some scrolling.
Positive side effect: When downloading is possible via TER detail page *only*, would more users eventually discover that there is a manual and a source repository in place.
## Optional
If the download button in search results is not removed: The download button could also be non-version-specific and just point to the TER detail page instead of initiating the download itself.Sprint 2018-03 (Release)