[Bug] Undefined array key in select2 field

[dluccajose]

Bug report

Please note: All issues must be submitted in English. If not, they will be closed automatically.

What I did

Used a relationship field (for a belongsTo relationship), filter the options using the 'options' key of the field like this

[
      'name' => 'executive_id',
      'label' => __('Executive'),
      'type' => 'relationship',
      'options' => function ($query) {
          return $query->executives();
      },
      'wrapper' => ['class' => 'form-group col-md-6'],
  ],

What I expected to happen

When i edit a record that their current value for the field executive_id is no longer available (because of the filter), it should displays empty

What happened

It thows an "Undefined array key x" error

What I've already tried to fix it

Modify the select.blade.php inside the relationship folder to check for the value first, this work but i think it should be something that is fixed in the package

Is it a bug in the latest version of Backpack?

After I run composer update backpack/crud the bug... is it still there?

yes

Backpack, Laravel, PHP, DB version

When I run php artisan backpack:version the output is:

### PHP VERSION:
8.2.26

### PHP EXTENSIONS:
Core, date, libxml, openssl, pcre, zlib, filter, hash, json, pcntl, random, Reflection, SPL, session, standard, sodium, mysqlnd, PDO, xml, ast, bcmath, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, igbinary, intl, exif, msgpack, mysqli, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, readline, shmop, SimpleXML, sockets, sqlite3, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, memcached, redis, Zend OPcache

### LARAVEL VERSION:
10.48.22.0

### BACKPACK PACKAGE VERSIONS:
backpack/basset: 1.3.6
backpack/crud: 6.7.41
backpack/generators: v4.0.7
backpack/permissionmanager: 7.2.1
backpack/pro: 2.1.13
backpack/settings: 3.1.1
backpack/theme-coreuiv4: 1.1.1

[backpack-ai-bot]

Based on the information provided in your bug report, it appears you're experiencing an issue with the relationship field in Backpack CRUD when using the 'options' key to filter the available options. This is indeed a known issue that has been reported and discussed in the Backpack community. Let me provide some insights based on the available knowledge sources.

The problem you're encountering is similar to an issue reported in Github Issue #5378, where using a 'select' type with a relationship was causing errors. While your specific error message is different, the underlying cause might be similar.

In your case, the error occurs when editing a record where the current value for the executive_id field is no longer available due to the filter you've applied. This suggests that Backpack is not properly handling cases where the current value doesn't exist in the filtered options.

Your workaround of modifying the select.blade.php file to check for the value first is a valid temporary solution. However, you're correct in thinking that this should be addressed in the package itself.

Unfortunately, the knowledge sources don't provide a direct fix for this specific issue. However, here are a few suggestions based on similar problems:

1. Make sure you're using the latest version of Backpack CRUD. You're currently on version 6.7.41, which is recent, but it's worth checking if there's a newer version available that might have addressed this issue.

2. Consider opening a new issue on the Backpack CRUD GitHub repository, providing your specific use case and error message. This will help the maintainers address the problem in a future release.

3. As a temporary workaround, you could modify your options function to include the current value of the field, even if it doesn't match your filter criteria. This would prevent the "Undefined array key" error, although it might not be ideal for your use case.

4. If possible, consider using the select2_from_ajax field type instead, which might handle this scenario better. However, this would require changes to your implementation.

Given that this issue persists in the latest version you're using, it's likely a bug that needs to be addressed by the Backpack team. I recommend reporting this issue on their GitHub repository with your specific use case and error message for further assistance and to help improve the package for all users.

ℹ️ Please note our AI Bot does not reply to follow-ups, this will be the only AI answer in this thread. If the AI helped you find the answer, please mark it as answered or write details below so it can learn. Then close the conversation. If not, please give more information for when a human reads this. ℹ️

Relevant sources:

Github Issue (closed): [Bug] Update Trait: bad array key checking $field['subfield']
Github Issue (closed): [Bug] options attribute ignored in relationship field type
Github Issue (closed): [Bug] In the edit form, the relationship field does not keep its value (select).
Github Issue (closed): [Bug] Undefined array key "relation_type"
Github Issue (closed): [Bug] Backpack v5 breaks morphTo select field
Github Issue (closed): select is not working in relationship
Github Issue (closed): [Bug] Relationship field are not displaying good selected values on setupUpdateOperation
Github Issue (closed): Empty name for subfields not handling properly
Github Issue (closed): [Bug] "Undefined index: pivot" on modifyField
Github Issue (closed): Relationship select not working
Github Issue (closed): [Bug] Undefined array key "attribute" while filtering
Github Issue (closed): [Bug] Search is not working correctly
Github Issue (closed): [Bug] When using 'select' type with morphToMany relationship, it errors.
Github Issue (closed): [Bug] incorrect work select2_from_array field as subfield relationship
Github Issue (closed): [4.1.x] New relationship field

[jcastroa87]

Hello @dluccajose

Thank you for sharing the details of the issue. To better understand the situation and assist you more effectively, could you please provide the following?
1. A screenshot or full error message showing the “Undefined array key x” error you’re encountering.
2. Details of the modifications you made to the select.blade.php file in the relationship folder to resolve the issue.

This information will help us pinpoint the problem and suggest the best possible solution.

Looking forward to your reply!

Cheers.

[dluccajose]

Sure @jcastroa87,

1. Relationship field with a filter in the query

https://imgur.com/4Y7hdrx

2. Error when you go to edit a entry where the current 'type' its no available (has is_active value in 0)

https://imgur.com/GnF5164

3. The line change in the select.blade.php file to fix the issue

https://imgur.com/2Lmc2CO

[jcastroa87]

Thanks @dluccajose

I will check about this and if the issue is confirmed, we will work in a fix in the next releases.

Cheers.

[jcastroa87]

Hello @dluccajose,

Thank you for pointing this out!

The pull request has been created and is currently being tested by our team. If everything goes well, it will be merged shortly.

We appreciate your attention to detail and your contribution!

Cheers.