Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When changing PhpStorage to use the non-secure, plain FileStorage via settings.php, in order to be able to debug/edit dumped PHP files, like this:
$conf['php_storage']['default']['class'] = 'Drupal\Component\PhpStorage\FileStorage';
(Background: You cannot touch/debug/edit dumped PHP files with the MTime*Storages.)
...then you get this PHP warning in many places, whenever ::save() is invoked:
mkdir(): File exists
Warning FileStorage.php 56 Drupal\Component\PhpStorage\FileStorage->save()
Comment | File | Size | Author |
---|---|---|---|
#1 | drupal8.php-file-save.1.patch | 602 bytes | sun |
Comments
Comment #1
sunThis patch fixes it.
Comment #2
sunmmm... looks like no one is using the bare PhpStorage\FileStorage.
This issue actually has nothing to do with Windows... Just simply not using the default PhpStorage\MTimeProtectedFileStorage implementation (jesus, what a name...).
I'm getting a complete dump of the Kernel container + PHP warning (as exception in tests), each time the kernel is rebuilt, which leads to plenty of false-positive test failures. :(
So please excuse me for going out of line of procedures here, but these error messages are really getting annoying :-/
Comment #3
moshe weitzman CreditAttribution: moshe weitzman commentedLooks fine. RTBC is legit.
Comment #4
sun"Thanks" to this bug, I was at least able to discover #1897468: Kernel rebuilds service container on every request when a module vanishes ;)
So yeah, once in a while, bugs are indeed features :P
Comment #5
catchLooks fine. Committed/pushed to 8.x.
Comment #6.0
(not verified) CreditAttribution: commentedUpdated issue summary.