Closed (fixed)
Project:
Automatic Updates
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Jun 2019 at 20:18 UTC
Updated:
27 Jun 2019 at 19:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
heddnComment #3
heddnHere we add a basic test.
Comment #4
heddnComment #5
heddnComment #6
heddnComment #7
heddnSo, the testbot runs things in an "interesting" way when it comes to PHP_SAPI. This should make it and running tests locally happy. Fingers crossed.
Comment #8
heddnMost of this is a straight port. The lone item I think of interest:
This is a poor-mans way to register checkers as certain priorities and categories. And let's us keep much of the D8 logic intact. Any concerns with this approach?
Don't let it confuse you that we have the same checker registered twice. I want to get this in quickly and once we add an actuall error level checker, we can remove the PhpSapi checker from here.
Comment #9
heddnComment #10
catchGenerally this looks good, only concern I have is no we're back to Drupal 7 and variable_set() that there's potentially a lot of variable_set() calls.
Is it worth comparing $messages with the current value to avoid the variable_set() if there's been no changes?
There's no $category on the end here - does this mean we're setting this multiple times during the same run? Ideally we'd do it in automatic_updates_run_checks() after the foreach to avoid duplicate writes.
Comment #11
heddnThis should address the concerns w/ variable_set. The checker manager is called from cron and an admin form so we should encapsulate as much in the manager as possible.
Comment #12
catchThanks!
Comment #14
heddnThis now unleashes the possibility to easily backport the rest of the readiness checkers.