[5.x]: @storage/runtime doesn't exist or isn't writable by PHP. Please fix that. (potential 5.10.4 regression)

[jamesmacwhite]

What happened?

Description

I am getting the following error on Craft CMS 5.10.4 app, I think possibly related to #18936. For reference, I am not modifying anything to do with the storage/runtime path or setting in config/app.php in any custom way.

@storage/runtime doesn't exist or isn't writable by PHP. Please fix that.

As the path is literally being created as @storage/runtime the alias for @storage is not being parsed. This was in a console context, rather than web requests.

I think this is potentially a regression.

Craft CMS version

5.10.4

PHP version

8.4

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions

[linear-code]

CMS-2139

[jamesmacwhite]

I think this is broken as a literal @storage/runtime path is created, not /storage/runtime

[jamesmacwhite]

And further fun, you'll have a harder time downgrading due to the Twig advisories for 3.26.

[ingolfurs]

Can confirm this is breaking deployments on our end too.

[jamesmacwhite]

Yeah I'd downgrade for now, the storage path is basically broken in 5.10.4, when you install 5.10.4, you'll find a literal @storage folder in the root of your project.

I downgraded to 5.10.3 temporarily, although have had to remove some protection against vulnerable dependencies given the Twig 3.26 sandbox disclosure.

[arcustech]

Have not tested, not in a location I can at the moment, but if you replace the created @storage with a symlink to the proper location does this work around the issue on a temp basis?

[michtio]

@jamesmacwhite I have the same issue, right now. After a composer update. Which made our client go offline .... Only got it after deployment, not locally.

[jamesmacwhite]

Have not tested, not in a location I can at the moment, but if you replace the created @storage with a symlink to the proper location does this work around the issue on a temp basis?

Maybe, but if you use serverless or don't have access to the server, not really viable, downgrading for now is best.

[jamesmacwhite]

@jamesmacwhite I have the same issue, right now. After a composer update. Which made our client go offline .... Only got it after deployment, not locally.

It seems to be more on console requests, than web, but not entirely sure.

[arcustech]

Have not tested, not in a location I can at the moment, but if you replace the created @storage with a symlink to the proper location does this work around the issue on a temp basis?

Maybe, but if you use serverless or don't have access to the server, not really viable, downgrading for now is best.

That is true, but best to offer options if someone can't downgrade for other reasons and does have access too. Possible options are always good.

[jamesmacwhite]

Totally. Downgrading is tricky at the moment if you use security packages due to the Twig 3.26 vulnerabilities you have to temporarily remove these to prevent composer update being blocked, however looks like @timkelty is on it with a draft PR:

#18986

[brandonkelly]

Craft 5.10.4.1 is out with a fix for this. Thanks all! And sorry for the trouble.