Failed to unlink file

Created on 15 March 2021, over 3 years ago
Updated 9 November 2023, about 1 year ago

Problem/Motivation

First I ge the error about css folder is not created inside background_image folder
I create the folder and the module begin to work I can see the image.

But after sometime I get the error:

Failed to unlink file public://background_image/css/x/public/numbersofcsscreate.css.gz'.

And the image stop to show

Im trying changing folder permissions but I dont get any result.

💬 Support request
Status

Closed: works as designed

Version

2.0

Component

Documentation

Created by

🇲🇽Mexico koffer

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇩🇰Denmark ressa Copenhagen

    It looks like Drupal changes permissions for js and css folders after an update, see #3369960-7: type error on drush cr for more.

  • Status changed to Closed: works as designed about 1 year ago
  • 🇦🇺Australia Nigel Cunningham Geelong

    Thanks for raising the issue but I don't believe this will be an issue with the module itself; it doesn't try to mess with permissions so they'll depend on your particular filesystem's configuration.

    I'll close the issue as "works as designed" but if you have info that proves me wrong, please feel free to reopen it.

    Thanks!

  • For others, I also have my website with the webserver set as the group not the file owner, I guess we could make the web serve the owner of the files directory but I would rather not.

    So after using drush frequently I get something like
    ...Permission denied FileSystem.php...
    [error] Failed to unlink file 'assets://css/css_....

    So to not see this I adda step reset permissions for the folder used by css injector.
    like... chown -R user:www ./files
    then su - user
    then run drush.

    I only have this issue with the module, it is a good module, a simple work around since this module "works as designed"

Production build 0.71.5 2024