πŸ‡¬πŸ‡§United Kingdom @jollysolutions

Account created on 3 September 2013, over 11 years ago
#

Recent comments

πŸ‡¬πŸ‡§United Kingdom jollysolutions

I added your patch and drush updb. The error still occurs and the exported config did not change. :(

πŸ‡¬πŸ‡§United Kingdom jollysolutions

jollysolutions β†’ changed the visibility of the branch 3499720-mixed_so_it_works_for_now to hidden.

πŸ‡¬πŸ‡§United Kingdom jollysolutions

jollysolutions β†’ changed the visibility of the branch 3499720- to hidden.

πŸ‡¬πŸ‡§United Kingdom jollysolutions
langcode: en
status: true
dependencies:
  config:
    - field.storage.user.field_phone_number
  module:
    - disable_field
    - required_api
    - telephone
    - telephone_validation
    - user
third_party_settings:
  required_api:
    required_plugin: default
    required_plugin_options: {  }
  disable_field:
    add_disable: none
    edit_disable: none
  telephone_validation:
    format: 0
    country: {  }
id: user.user.field_phone_number
field_name: field_phone_number
entity_type: user
bundle: user
label: 'Phone Number'
description: 'Please enter the number with +44 at the front and omitting the leading zero for example +447700900000 instead of 07700900000.'
required: {  }
translatable: false
default_value: {  }
default_value_callback: ''
settings: {  }
field_type: telephone

an example of a config field where this happens

πŸ‡¬πŸ‡§United Kingdom jollysolutions

They are blank arrays in config. I tried to set them to FALSE and do a config import but on the very next export they change back to empty arrays

πŸ‡¬πŸ‡§United Kingdom jollysolutions

jollysolutions β†’ changed the visibility of the branch 3499720-major-error-on to hidden.

πŸ‡¬πŸ‡§United Kingdom jollysolutions

changing the isRequired from bool to mixed removed the error for me, I am unsure why some field definitions are arrays instead of bools

πŸ‡¬πŸ‡§United Kingdom jollysolutions

jollysolutions β†’ made their first commit to this issue’s fork.

πŸ‡¬πŸ‡§United Kingdom jollysolutions

patch applies and empty messages do not trigger warnings

πŸ‡¬πŸ‡§United Kingdom jollysolutions

Your MR worked and no errors.

πŸ‡¬πŸ‡§United Kingdom jollysolutions

I have the warning show even if the message is empty. It shows an empty warning message

The patch does not apply to the latest dev version but when applied to 2.1.0 the blank warning does not appear.

πŸ‡¬πŸ‡§United Kingdom jollysolutions

On updating the module and performing a

drush updb

I get the following error

 ------------------ ----------- --------------- ----------------------------------------------
  Module             Update ID   Type            Description
 ------------------ ----------- --------------- ----------------------------------------------
  required_by_role   8001        hook_update_n   8001 - Clean up the required_plugin_options.
 ------------------ ----------- --------------- ----------------------------------------------


 // Do you wish to run the specified pending updates?: yes.

>  [notice] Update started: required_by_role_update_8001
>  [error]  array_filter(): Argument #1 ($array) must be of type array, int given
>  [error]  Update failed: required_by_role_update_8001
 [error]  Update aborted by: required_by_role_update_8001
 [error]  Finished performing updates.
πŸ‡¬πŸ‡§United Kingdom jollysolutions

The patch in #7 works on Drupal 10 please commit and release.

πŸ‡¬πŸ‡§United Kingdom jollysolutions

Could that be an option? Whether to delete the references or not? And if the reference was used else where would it not be reimported ie on the next cron?

Production build 0.71.5 2024