[Bug] Trying to access array offset on value of type null

[lukepower]

Bug report

What I did

After following the automatic installation, when trying to create a new model (even without adding any particular filed), when saving I end up with a 500 error.

'Trying to access array offset on value of type null'

What I expected to happen

The new model to be at least saved.

What happened

Got a 500 error Trying to access array offset on value of type null

What I've already tried to fix it

Tried to simplify the new model to the bare minimum. Also, restarting Mysql or php artisan serve, as well as a composer update. No change.

Backpack, Laravel, PHP, DB version

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

PHP VERSION:

PHP 8.1.2 (cli) (built: Jan 19 2022 10:18:23) (ZTS Visual C++ 2019 x64)
Copyright (c) The PHP Group
Zend Engine v4.1.2, Copyright (c) Zend Technologies
with Xdebug v3.1.2, Copyright (c) 2002-2021, by Derick Rethans

LARAVEL VERSION:

v9.48.0@c78ae7aeb0cbcb1a205050d3592247ba07f5b711

BACKPACK PACKAGE VERSIONS:

backpack/crud: 5.0.19
backpack/pagemanager: 3.0.11
backpack/permissionmanager: 6.0.15
backpack/pro: 1.0.18
backpack/generators: v3.1.13

Operating System and Server Setup

I encountered the problem above on my Windows 10 machine, and my web server is set up using XAMPP.

[pxpm]

Hello @lukepower thanks for the report 🙏

I will need a bit more to try to figure out what's going on. Can you share with me the flare page error, or post some more details about the error ?

You can probably find more details on storage/logs/laravel.log file.

Any chance you could update backpack dependencies, so that we make sure we are not talking about some issue that we had previously fixed ? We are currently on Backpack 5.4, it should be a non-breaking update 👍

Don't forget to republish assets after update with: php artisan backpack:publish-assets.

Cheers

[lukepower]

Error is this:
'{
"class": "ErrorException",
"message": "Trying to access array offset on value of type null",
"code": 0,
"file": "F:\Programming\new-remote-skygems\vendor\laravel-shift\blueprint\src\Tracer.php:120",
"trace": [
"F:\Programming\new-remote-skygems\vendor\laravel\framework\src\Illuminate\Foundation\Bootstrap\HandleExceptions.php:266",
"F:\Programming\new-remote-skygems\vendor\laravel-shift\blueprint\src\Tracer.php:120",
"F:\Programming\new-remote-skygems\vendor\laravel\framework\src\Illuminate\Collections\Traits\EnumeratesValues.php:236",
"F:\Programming\new-remote-skygems\vendor\laravel-shift\blueprint\src\Tracer.php:121",
"F:\Programming\new-remote-skygems\vendor\laravel-shift\blueprint\src\Tracer.php:33",
"F:\Programming\new-remote-skygems\vendor\laravel-shift\blueprint\src\Commands\TraceCommand.php:51",
"F:\Programming\new-remote-skygems\vendor\laravel\framework\src\Illuminate\Container\BoundMethod.php:36",
"F:\Programming\new-remote-skygems\vendor\laravel\framework\src\Illuminate\Container\Util.php:41",
"F:\Programming\new-remote-skygems\vendor\laravel\framework\src\Illuminate\Container\BoundMethod.php:93",
"F:\Programming\new-remote-skygems\vendor\laravel\framework\src\Illuminate\Container\BoundMethod.php:37",
"F:\Programming\new-remote-skygems\vendor\laravel\framework\src\Illuminate\Container\Container.php:663",
"F:\Programming\new-remote-skygems\vendor\laravel\framework\src\Illuminate\Console\Command.php:182",
"F:\Programming\new-remote-skygems\vendor\symfony\console\Command\Command.php:312",
"F:\Programming\new-remote-skygems\vendor\laravel\framework\src\Illuminate\Console\Command.php:152",
"F:\Programming\new-remote-skygems\vendor\symfony\console\Application.php:1022",
"F:'

As for updating, how am I supposed to be able to force CRUD 5.4? Seems that while composer selects it, it is not being installed...

[pxpm]

Hey @lukepower

You can do a "composer update backpack/crud".

What does it say? Any errors?

If you got any errors please post them here so that I can have a look at it to help you.

You can also do a "composer why backpack/crud" to check if some of your other packages is forcing the 5.0 version.

Let me know.

[lukepower]

`PS F:\Programming\new-remote-skygems> composer require backpack/crud:5.4.0 --with-all-dependencies
Info from https://repo.packagist.org: #StandWithUkraine
./composer.json has been updated
Running composer update backpack/crud --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires backpack/crud 5.4.0, found backpack/crud[5.4.0] but these were not loaded, likely because it conflicts with another require.
Problem 2
- backpack/pagemanager is locked to version 3.0.11 and an update of this package was not requested.
- backpack/pagemanager 3.0.11 requires backpack/crud ^4.0|^5.0 -> found backpack/crud[4.0.0, ..., 4.1.x-dev, 5.0.0, ..., 5.4.15] but these were not loaded, likely because it conflicts with another require.
Problem 3
- backpack/permissionmanager is locked to version 6.0.15 and an update of this package was not requested.
- backpack/permissionmanager 6.0.15 requires backpack/crud ^5.0 -> found backpack/crud[5.0.0, ..., 5.4.15] but these were not loaded, likely because it conflicts with another require.
Problem 4
- backpack/pro is locked to version 1.5.0 and an update of this package was not requested.
- backpack/pro 1.5.0 requires backpack/crud ^5.4.9 -> found backpack/crud[5.4.9, ..., 5.4.15] but it conflicts with your root composer.json require (5.4.0).
Problem 5
- backpack/devtools is locked to version 1.3.0 and an update of this package was not requested.
- backpack/devtools 1.3.0 requires backpack/crud ^5.3 -> found backpack/crud[5.3.0, ..., 5.4.15] but these were not loaded, likely because it conflicts with another require.
Problem 6
- backpack/generators is locked to version 3.3.12 and an update of this package was not requested.
- backpack/generators 3.3.12 requires backpack/crud ^5.3.11 -> found backpack/crud[5.3.11, ..., 5.4.15] but these were not loaded, likely because it conflicts with another require.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.`

[lukepower]

And:

laravel/laravel dev-master requires backpack/crud (^5.4)
backpack/devtools 1.3.0 requires backpack/crud (^5.3)
backpack/generators 3.3.12 requires backpack/crud (^5.3.11)
backpack/pagemanager 3.0.11 requires backpack/crud (^4.0|^5.0)
backpack/permissionmanager 6.0.15 requires backpack/crud (^5.0)
backpack/pro 1.5.0 requires backpack/crud (^5.4.9)

[pxpm]

Hey @lukepower, try updating the following in your composer.json:

        "backpack/crud": "^5.4",
        "backpack/permissionmanager": "^6.0",
        "backpack/pagemanager": "^3.0",
        "backpack/pro": "^1.5"

Run composer update again. Let me know if still some error in your output.

Cheers

[lukepower]

Thats exactly what I currently have:
"backpack/crud": "^5.4", "backpack/pagemanager": "^3.0", "backpack/permissionmanager": "^6.0", "backpack/pro": "^1.5.0",

[lukepower]

@pxpm I can uninstall pagemanager as I am not using it anymore, but permissionmanager seems to conflict with the version...

[lukepower]

Actually, digging further: I have been able to install the 5.4 version package:
laravel/laravel dev-master requires backpack/crud (^5.4)
backpack/devtools 1.3.0 requires backpack/crud (^5.3)
backpack/generators 3.3.12 requires backpack/crud (^5.3.11)
backpack/pro 1.5.0 requires backpack/crud (^5.4.9)

However, php artisan backpack:version Still returns:
backpack/crud: 5.0.19
backpack/pagemanager: 3.0.11
backpack/permissionmanager: 6.0.15
backpack/pro: 1.0.18
backpack/generators: v3.1.13

[pxpm]

Hey @lukepower thanks for getting back with an update.

Can you then try: composer clear-cache , composer dump-autoload, php artisan cache:clear and check again.

If the problem persists I would advise you to try to install one by one, starting: crud -> pro -> generators -> permissionmanager

Let me know how it goes.

Cheers

[lukepower]

nothing...
Is there a practical way of determining the effective version from the source files?

[pxpm]

You should be able to check that in your composer.lock file. use some text editor to search for backpack/crud in that file.

[lukepower]

"name": "backpack/crud",
"version": "5.4.15",
"source": {
"type": "git",
"url": "https://github.com/Laravel-Backpack/CRUD.git",
"reference": "146a08082ebf3ad2f88df3e18c9735ad57ff19e5"
},

So, I deleted the whole "backpack" folder in "vendor/":

• Downloading backpack/crud (5.4.15)
  • Downloading backpack/generators (3.3.12)
  • Downloading backpack/devtools (1.3.0)
  • Downloading backpack/pro (1.5.0)
  • Installing backpack/crud (5.4.15): Extracting archive
  • Installing backpack/generators (3.3.12): Extracting archive
  • Installing backpack/devtools (1.3.0): Extracting archive
  • Installing backpack/pro (1.5.0): Extracting archive

---

But still:
php artisan backpack:version

PHP VERSION:

PHP 8.1.2 (cli) (built: Jan 19 2022 10:18:23) (ZTS Visual C++ 2019 x64)
Copyright (c) The PHP Group
Zend Engine v4.1.2, Copyright (c) Zend Technologies
with Xdebug v3.1.2, Copyright (c) 2002-2021, by Derick Rethans

LARAVEL VERSION:

v9.48.0@c78ae7aeb0cbcb1a205050d3592247ba07f5b711

BACKPACK PACKAGE VERSIONS:

backpack/crud: 5.0.19
backpack/pagemanager: 3.0.11
backpack/permissionmanager: 6.0.15
backpack/pro: 1.0.18
backpack/generators: v3.1.13