[#42421] - From Joomla 4.4.1 - Notes on the update source ...could not be found
- Closed
- 29 Nov 2023
- Medium
- Build: 5.0-dev
- # 42421
Who came up with this again and didn't think about the consequences?
We receive inquiries here in the Joomlaplates forum as to why these errors for our template updates and modules are suddenly displayed in the backend of J4.4.1.
Previously, our existing updates were always displayed, which were not provided on the update server and only had to be downloaded with a valid subscription and then installed in the backend. How should I set this in the backend so that it is displayed as before. I didn't find a function for activation or deactivation.
I can't deactivate all the update sources now and no longer receive any notifications?
No matter what, PLEASE turn it back quickly.
Execution:
Backend /Extensions /Check for updates
Result:
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
Yes and no. If updates are only displayed as a notice but a download is only possible on the manufacturer's website, the message is repeatedly shown that the update source is not available even though it exists. No Codce 200 (OK) comes back and it is then interpreted as shown in the view. But if I now deactivate the affected update source, it will no longer be displayed when there is a new xml file. It is clear that this must then be downloaded from the developer with a login. I hope you understand what i mean...
Wow, it only seems to affect Joomla installations at Strato and 1und1.
Can you possibly confirm that?
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-11-29 16:53:40 |
| Closed_By | ⇒ | WM-Loose |
It was already there with Joomla 4.4.0. I'll close the thread and we'll have to see what the problem is.
The culprit and problem is clearly the hoster Strato. We installed the Joomla installation 1:1 with another provider (DB version and PHP version identical) and there were no more errors when retrieving the update server. The website also has significantly faster loading times than Strato. We found out that the provider has probably been struggling with network problems for a long time. We will recommend the customer to choose another provider.
I think what you meant to say is that we are not following the documented process for extension updates and what can we do to fix that.