Thank you for beta testing! These instructions describe how to install the Automatic Updates module into a Drupal site, and use it to update Drupal core.
Please report your test result when finished.
php --version or visit /admin/reports/status/php in your Drupal site to confirm what version is installed. composer --version to find out what version of Composer you have. If it's older than 2.3.5, run composer self-update --2.Once the pre-requisites are fulfilled, you can either test with a new Drupal site or install Automatic Updates in an existing site.
composer create-project drupal/recommended-project:9.3.9 test --no-interaction
cd test
composer require 'drupal/automatic_updates:^2@beta' --no-interaction --with-all-dependencies
cd web
php ./core/scripts/drupal quick-start standard
composer require 'drupal/automatic_updates:^2@beta' --with-all-dependenciesYou may run into a known issue or limitation; see the project page for more information.
If you have Drush installed: There is a known issue where Drush installs a dependency that contains symbolic links, which can cause Automatic Updates to fail. To get around this, we recommend configuring Automatic Updates to use rsync, if you have it available; run which rsync or whereis rsync to determine its location, if it's installed. Then, run the following commands (replace /full/path/to/rsync with the actual path to rsync):
drush config:set package_manager.settings file_syncer rsync
drush config:set package_manager.settings executables.rsync /full/path/to/rsync
Thanks for testing! Please let us know how it went.
Were these instructions unclear or inaccurate? Please leave a comment on this issue to tell us about it.
| Comment | File | Size | Author |
|---|---|---|---|
| #48 | Screen Shot 2022-04-28 at 4.14.08 PM.png | 255.5 KB | p.ayekumi |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes, plain diff MR !281
Comments
Comment #2
Theresa.GrannumComment #4
Theresa.Grannum(empty)
Comment #5
tedbowComment #6
Theresa.GrannumComment #7
Theresa.GrannumComment #8
Theresa.GrannumComment #9
Theresa.GrannumComment #10
Theresa.GrannumComment #11
Theresa.GrannumComment #12
Theresa.GrannumComment #13
Theresa.GrannumComment #14
Theresa.GrannumComment #15
Theresa.GrannumComment #16
Theresa.GrannumComment #17
Theresa.GrannumComment #18
kunal.sachdev commentedWhile trying these steps, in the section 'Use Automatic Updates to update Drupal' I found following:
i) The 1st point says 'Click the "Updates" tab.' , I think it should be "Update" instead of "Updates".
ii) The 3rd point says 'Click the "Download these updates" button.' , I think it should be "Download" instead of "Download these updates".
Comment #19
Theresa.GrannumUpdated wording per feedback from Kunal
Comment #20
Theresa.GrannumComment #21
Theresa.GrannumComment #22
phenaproximaComment #24
phenaproximaComment #25
phenaproximaComment #26
phenaproximaComment #27
Theresa.GrannumComment #28
Theresa.GrannumComment #29
Theresa.GrannumComment #30
Theresa.GrannumComment #31
Theresa.GrannumComment #32
phenaproximaComment #33
phenaproximaComment #34
phenaproximaComment #35
phenaproximaComment #36
phenaproximaComment #37
phenaproximaComment #38
phenaproximaComment #39
tedbowComment #40
phenaproximaUpdated instructions with rsync workaround for Drush.
Comment #41
phenaproximaComment #42
phenaproximaComment #43
mradcliffeI am going to attempt to run through the beta instructions at Portland2022 and provide feedback about the instructions after I am done.
Comment #44
mradcliffeI do not have access to update composer as a regular user on my linux box. I needed to run sudo, but other people may have it installed via package / homebrew / Windows installer.
Directory = directory with composer.json on existing site
I reached up to the "Use Automatic Updates to update Drupal" section, but I won't be able to finish reviewing the instructions until I setup a new site later.
If we want to still have a beta result, then maybe change the instructions to mention that I/we should still post beta result issue even if we are already up-to-date?
Or mention that for an existing site, we should use an outdated site first?
Comment #45
shiraz dindarIn "Testing with an existing Drupal Project", step #2 needs to have the project in single quotes, ie. changed to:
Run: composer require 'drupal/automatic_updates:^2@beta'This also needs to be changed on the main project page under "Installation"
Otherwise, composer will fail with "no matches found"
Comment #46
p.ayekumiIn the instructions under the "Install Automatic Updates module" #5 you will see a pop up saying the following.
You must enable the Automatic Updates 9.3.x shim, Package Manager modules to install Automatic Updates.
• The following modules are experimental: Automatic Updates, Package Manager
Would you like to continue with the above?
This message does not tell you that it will actually automatically add install Automatic Updates 9.3.x shim.
Comment #47
tedbowadd single quotes in the other composer command
Comment #48
p.ayekumiWhen I was trying to Use Automatic Updates to update Drupal under
#3 (Click the "Update" button. You should be redirected to a page with a progress bar.)
At this point after it a while I received an error page (Please reference the attached image)
When I clicked the link to the "Please continue to the error page link"
I ran into Timeout on composer require error page.
After trying to redo the step #3 I received the same error page that you see in the attached photo but now the page has timed out and will not go back to the error page saying that it is Timed out for 120 sec.
Please reference Automatic Update Error
Comment #49
farnoosh commentedIt would be better to know about the requirement of the exsting drupal project. I would move the "make sure your existing drupal project is not fully up to date" somewhere before choosing "Testing with an existing Drupal Project" section.
Comment #50
ressaThe instructions are clear and accurate, and I updated Drupal to the latest version following them.
I couldn't help myself from also trying the Automatic Updates Extensions module. It also worked perfectly, and I successfully updated the Token module from 8.x-1.8 to 8.x-1.10 via the GUI, nice!
Comment #51
phenaproximaAdding the
--with-all-dependenciesflag to the Composer commands in the issue summary, to prevent dopey errors like the ones described in #3282693: [DrupalCon] Automatic Updates beta test result.Comment #52
gábor hojtsyThanks for all the testing efforts folks! Automatic updates is out of beta and we are looking to expand testing to hosting environments. I cloned this issue to #3308319: Automatic updates 8.x-2.x testing guide for hosting environments and updated the instructions slightly for that.