Composer Permissions Issue

trellis
1

Hi,

I’m having an issue updating Wordpress via Composer using Trellis and Bedrock.

When I use the Composer Update script via terminal I get the following error:

    Updating johnpbloch/wordpress-core (4.8.0 => 4.8.1):     Update failed (Could not delete web/wp/wp-includes/js/tinymce/plugins/charmap/plugin.js: )
    Would you like to try reinstalling the package instead [yes]? yes
  - Removing johnpbloch/wordpress-core (4.8.0)

                                                                              
  [RuntimeException]                                                          
  Could not delete web/wp/wp-includes/js/tinymce/plugins/charmap/plugin.js:

I tried removing the files manually and installed again and got this:

  - Installing johnpbloch/wordpress-core (4.8.1): Downloading (100%)         
  - Updating johnpbloch/wordpress (4.8.0 => 4.8.1):     Update failed (Could not delete /srv/www/logiclofts.co.uk/current/vendor/johnpbloch/wordpress/composer.json: )
    Would you like to try reinstalling the package instead [yes]? no

                                                                                                  
  [RuntimeException]                                                                              
  Could not delete /srv/www/logiclofts.co.uk/current/vendor/johnpbloch/wordpress/composer.json:

I then deleted the johnpbloch folder and it installed fine. It’s not ideal to manually delete the files every time though.

I think it’s a permissions problem from the VM. I’m using an existing Trellis install but a fresh Bedrock install. This is the first time I’ve tried to update Wordpress.

Has anyone come across this?

Thanks

Rob

1 Like
2

This is an annoying Vagrant bug that still isn’t fixed

I use finder to change the permissions when this happens (sometimes multiple times a day)

2 Likes
3

A workaround waiting for the bug to be fixed. From your host machine, perform the following command in the Bedrock folder:

ls -alR > /dev/null

6 Likes
4

Worked for me, thanks!

1 Like
5

Hey guys. I’m having the same problem, even if I run the command. Plus I’m having composer caching problems after running it. @ben how did you manage to make it work?

Thanks!

6

By doing exactly as mentioned in the post. There are also other workarounds as mentioned in the Vagrant issue I linked

7

Hi flocca, this worked for me. Thanks!

1 Like
8

Awesome, thanks @flocca!

1 Like
10

For what it’s worth, I am on 10.13.1 and I’ve tried every option suggested so far, and nothing seems to be working. Still digging.