[#17969] - Duplicate extension entries when a extension is using two update servers
- Closed
- 19 Dec 2019
- Medium
- Build: staging
- # 17969
Steps to reproduce the issue
Install a extension that uses a collection and extension update server (similiar should happen with multible update servers too)
Expected result
Just one entry that indecate compatibility or not
Actual result
On entry per update server that indecate compatibility or not.
System information (as much as possible)
Additional comments
cc @wilsonge
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Category | ⇒ | com_installer |
| Title |
|
||||||
| Status | New | ⇒ | Information Required |
You can checkout any of my extensions ;) For example you can use this:
Key 56D3152A0EC8698E4D3CAD1317D484EB110
Download: https://www.jah-tz.de/download-bereich.html
any Suggestion @brianteeman?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/17969.
What is the use case for having the two update servers. It sounds weird.
What is the use case for having the two update servers. It sounds weird.
Nothing spezial but give the design of the update server this is possible and supported so we should fix that issue ;)
The idea behind that could be the priority tag or a different updateserver in case one domain is down etc.
What is the use case for having the two update servers. It sounds weird.
It isn't really (;
For example, currently in Russia many users are unable to update Joomla because some ISPs block AWS IP adresses.
http://m.cnews.ru/news/top/2017-09-26_v_rossii_zablokirovali_dostup_k_sverhpopulyarnomu
| Status | Information Required | ⇒ | Discussion |
| Status | Discussion | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-01-13 12:59:07 |
| Closed_By | ⇒ | zero-24 |
wilsonge
- | Status | Closed | ⇒ | New |
| Closed_Date | 2018-01-13 12:59:07 | ⇒ | |
| Closed_By | zero-24 | ⇒ |
| Labels |
Added:
?
|
||
I have been told that my setup is weird without any other voice raised in months (the fallback for blocked AWS is implemented in a different way already) I decided to close it as no issue. So correct there is no PR yet. ;)
| Status | New | ⇒ | Discussion |
| Labels |
Added:
J3 Issue
|
||
| Title |
|
||||||
| Title |
|
||||||
| Status | Discussion | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-12-19 14:59:12 |
| Closed_By | ⇒ | zero-24 | |
| Labels |
Added:
?
Removed: ? |
||
| Labels |
Removed:
?
|
||
Can you give an example extension that is affected by this?