Bug: Using asset() helper causes failures when running WP-CLI commands

[retlehs]

Description

The asset function works until a wp command is ran

Steps To Reproduce

1. Use the asset() helper in a PHP file:

add_action('init', function () {
    $test = asset('editor.css');
});

2. Run wp

Actual Behavior

Fatal error: Uncaught ReflectionException: Class "assets.manifest" does not exist in /srv/www/example.com/current/web/app/themes/sage/vendor/illuminate/container/Container.php:893

Versions

v3.0.0

[QWp6t]

Hey @retlehs 👋

Thanks for reporting this! 🙏

I'll look into it this weekend and see about getting a fix implemented!

[retlehs]

Note: Others may also be getting this same error message in a situation that is unrelated to this bug — this is the result of having an outdated config/app.php file in your setup. If you're running into this error and aren't using the asset() helper, see the Upgrade Guide for info

[retlehs]

FWIW, the hook used definitely matters, too:

• ✅ Using asset() in wp_head
• ❌ Using asset() in init
• ❌ Using asset() in after_setup_theme

[Twansparant]

Don't know if it's related, but running wp acorn optimize without the asset() function call, also results in an error:

In ConfigCacheCommand.php line 84:
                                                  
  Your configuration files are not serializable.  
                                                  

In config.php line 336:
                                                   
  Call to undefined method Closure::__set_state()  
                                                   

This also seems to slow down the wp admin significantly.

[QWp6t]

@Twansparant

That looks to me like there are some closures getting into your config somewhere, which aren't serializable out of the box and should be avoided in your configs.

It's also possible that we missed a dependency from Laravel 9 that we need to get in there, such as laravel/serializable-closure.

I'll dig into these issues tomorrow.

[Twansparant]

That looks to me like there are some closures getting into your config somewhere, which aren't serializable out of the box and should be avoided in your configs.

This error was caused by my log1x/poet config file.
I was using the Extended CPTs Admin Columns Custom Function in a few of my CPT's.

I moved my function to a class like suggested here, and the error is gone!