Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Follow-up to #2159501: Remove DRUPAL_BOOTSTRAP_DATABASE
Focus on removing the bootstrap phase (only).
Blocked on:
Comment | File | Size | Author |
---|---|---|---|
#7 | drupal8.bootstrap-variables-die.7.patch | 7.74 KB | sun |
drupal8.bootstrap-variables-die.0.full_.patch | 6.74 KB | sun | |
drupal8.bootstrap-variables-die.0.patch | 7.08 KB | sun | |
Comments
Comment #2
ianthomas_ukWhat is the advantage of removing DRUPAL_BOOTSTRAP_VARIALBES before removing the variable subsystem?
This backwards compatibility hack looks fairly safe, but I'd hate for us to waste time tracking down bugs it introduced when we could have just waited.
Comment #4
xjmThis is either critical and a beta blocker in its own right, or a duplicate of #2167109: Remove Variable subsystem. I think it's fine to scope it separately for now and then mark it duplicate later if needed.
Comment #5
ianthomas_ukOn further thought, I think the backwards compatibility code would be broken by someone setting $conf in settings.php. Is it better just to do this as part of #2167109: Remove Variable subsystem?
Comment #6
larowlanThis will be blocked on the language cmi conversions.
Comment #7
sunInteresting. Given a test failure difference of 1 between both patches, and the fact that non-language related tests passed, I wonder how attached patch performs - copypasting the lazy-instantiation concept to _set() + _del(). :)
Comment #9
sunMerged into #2167109: Remove Variable subsystem
Comment #10
xjm