cloudflare_update_8003 [error] The configuration property zone_id.0.0 doesn't exist

Open on Drupal.org →

Created on 30 March 2023, almost 2 years ago

Problem/Motivation

After updating from Beta2 to Beta3 our tugboat preview environments are failing to properly run the latest cloudflare updates. It works fine on our local environments however. The tugboat previews are on a different domain however, thats all I can think of.

Module Update ID Type Description
cloudflare 8003 hook_update_n 8003 - Cloudflare to support multiple zones for multiple domains.
cloudflare 8004 hook_update_n 8004 - Cloudflare to support multiple zones for multiple domains.
cloudflare 8005 hook_update_n 8005 - Set ....

// Do you wish to run the specified pending updates?: yes.
[notice] Update started: cloudflare_update_8003
[error] The configuration property zone_id.0.0 doesn't exist,
[error] Update failed: cloudflare_update_8003
[error] Finished performing updates.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report

Status

Active

Component

Code

Created by

🇺🇸United States NicholasS

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Merge Requests

!16cloudflare_update_8003 [error] The configuration property zone_id.0.0 doesn't exist
Open
🇸🇮Slovenia icurk
updated 12 months ago

Comments & Activities

Issue created by @NicholasS
Comment almost 2 years ago →
🇺🇸United States NicholasS
Comment almost 2 years ago →
🇬🇧United Kingdom webfaqtory
I have this problem as well
First commit to issue fork.
Merge request !16Fix issue with the hook_update #8003 when zone id is already stored as an array. → (Open) created by icurk
Open in Jenkins → Open on Drupal.org →
Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
last update 12 months ago
59 pass
Status changed to Needs review 6 days ago4:29pm 23 January 2025
Comment 6 days ago →
🇦🇹Austria granik Vienna
I'm currently having the same problem on 2.0.0-beta1, so I updated the issue metadata.
@icurk, thanks for your merge request, I tried to apply the diff and now the error is gone. I guess it's at least a workaround for the issue.

P.S. I've added the MR diff as a patch file here as well to simplify composer patching :)

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024