-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port or build a shim for update.module to fix "There was a problem checking available updates for Backdrop." #396
Comments
By the way, when checking manually, it is also giving:
|
@AlexShapka: There currently is no update server (what you might hear people referring to "mothership") for each installation to communicate with and check the update status against. This topic is part of the weekly meetings agenda and there is an issue filed for it. It's issue #22 in the .org issue queue. As for the issue you mention here, I have already reported this as part of #283. That one is a meta, so lets leave this issue here as the dedicated place for this specific issue (unless of course people think it's a duplicate of issue #22 in the .org issue queue). |
I updated the title of this issue. Let's make this the official issue for fixing update.module within Backdrop's code-base, while backdrop-ops/backdropcms.org#22 is the sys-ops portion of this. We talk about this every week in the status report meetings on Thursdays, but so far we haven't had the time or any volunteers to take on this issue. What we will likely do for the initial release of Backdrop 1.0 is simply quiet the errors if the remote server is not available. We'll point update.module at update.backdropcms.org, but there won't be anything on the receiving end that actually functions. Then when we later get the update server working, update.module will start reporting as it should. Basically, the module will just connect to a shim until the real update server is ready. |
This is a 1.0.0 release blocker for sure. |
Would it be worth setting the default value of 'Check for updates automatically' and 'Receive e-mail notifications' to FALSE in the install profile while this is unfinished? |
We'd really like to encourage people leaving these options enabled so that when the update server starts working, we'll be able to track these sites. I'm going to start working on this issue; I don't think adding shim functionality is going to be very difficult. |
PR filed at backdrop/backdrop#604. Here are some before and after screenshots: As noted in backdrop-ops/backdropcms.org#22, we've now set up https://updates.backdropcms.org/release-history/ to return at |
I've merged in backdrop/backdrop#604 to address this critical problem. Now all we should need to do is re-implement the update server itself and all existing Backdrop sites will start receiving status updates. See backdrop-ops/backdropcms.org#22 for that issue. |
The status page is showing:
Backdrop CMS update status Up to date There was a problem checking available updates for Backdrop. See the available updates page for more information and to install your missing updates.
Clicking on
available updates
and then on(Check manually)
showsAll of your projects are up to date.
However, the status page still persists on error. Probably as two other issues I've just submitted this one is related to PHP version, which is PHP 5.4.16 in our case.
The text was updated successfully, but these errors were encountered: