Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
If the remote status is not set, an error occurs after ingesting the widgets and trying to add a new one.
Steps to reproduce
Ingest widgets, without the status set, and try to add a new one.
Proposed resolution
Set the unknown status whenever a new widget is about to ingest and the status doesn't exist.
Remaining tasks
Set unknown by default.
User interface changes
N/A
API changes
N/A
Data model changes
There wont be a null remote status, just unknown or the status set in the registry.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 3339913-7-unknown-as-default-remote-status.patch | 1.13 KB | isholgueras |
| #6 | 3339913-6-unknown-as-default-remote-status.patch | 1.13 KB | isholgueras |
| #2 | 3339913-2-unknown-as-default-remote-status.patch | 853 bytes | isholgueras |
Comments
Comment #2
isholgueras commentedHere is the patch to set 'unknown' as default remote status in the ingestion process.
The test probably will fail because it's using a constant added in this issue and the constant is not yet defined. At least until 3337158 is merged.
Comment #3
isholgueras commentedComment #4
e0ipsoWe need to update the dependency version in the composer.json once the Widget Type release is out.
Comment #5
e0ipsoWe need to update this patch to depend on widget_type 1.5.14.
Comment #6
isholgueras commentedHere is the patch with the composer require on
widget_type:"^1.5.14"Comment #7
isholgueras commentedI didn't have the branch 1.x updated. Here is the right patch
Comment #9
e0ipso