[DrupalCon] Automatic Updates local testing result

Created on 23 September 2022, about 2 years ago
Updated 8 December 2023, about 1 year ago

Thanks for testing Automatic Updates! Please tell us in detail about the problem you encountered. To help you, you can use the prompts below as guidance.

What was your goal? For example, what versions of Drupal core were you trying to update from and to?

I tried to use automatic_updates in an existing Drupal site.

D9 9.4.0 to 9.4.6

What were the steps you took, starting from when you added the Automatic Updates module to your Drupal project (see https://www.drupal.org/i/3275810#install-module β†’ for instructions)? Include anything that seems relevant, including commands you ran, links you clicked on, output logs, relevant config files, screenshots, screen recordings, etc.

According to your guideline I installed the module.

What was your environment like?
local environment in testing branch

Was this a local development environment, or a remote server?:

local environment in testing branch

Are you using Lando, DDEV, or another Docker-based environment?:
no

What operating system were you using?
Ubuntu 20.04.5 LTS

What web server are you using?
Apache2 2.4

What PHP version are you using (see https://www.drupal.org/i/3275810#confirm-php-version β†’ )?

What version of Composer are you using (see https://www.drupal.org/i/3275810#confirm-composer-version β†’ )?
Composer version 2.4.2

Did you accomplish your goal? Were the instructions clear? Did you observe any bugs or errors, or other issues? Did you need to do any workarounds?

Unluckily the installation failed. First I got more than one message from Messenger.

1. xdebug was enabled -> so I disabled xdebug
2. there were some symlinks in a local library, exactly the the C3.js library -> I disabled it; maybe I couldn't do than in a live environment
3. there were a message that write access is needed to the files -> I gave Apache full write access to that files

/web/sites/default/default.services.yml
/web/sites/default/default.settings.php

4. The cweagans/composer-patches plugin is installed, but the composer-exit-on-patch-failure key is not set to true in the extra section of /home/www/i3/apps/intranet/composer.json -> so I set the composer-exit-on-patch-failure key in my composer extras

After that -> ready to update, but it failed due write permissions for the webserver -> maybe the write permissions inside the configured tmp directory where not correctly set

Problem with these instructions? Anything else we should know?

The instructions were clear

πŸ› Bug report
Status

Postponed: needs info

Version

3.0

Component

Code

Created by

πŸ‡©πŸ‡ͺGermany martinelkb

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

    I was going to close this issue, but in retrospect, we don't know how many of these problems, if any, would still be encountered using the new 3.0.0 version. The 8.x-2.x version is effectively abandoned.

    So I'm postponing this, since we need more info. Just re-test the latest 3.0.x release on your setup, and let us know in here how it went.

Production build 0.71.5 2024