Problem with files permalink

[vpratfr]

This is related to: Varying-Vagrant-Vagrants/VVV#377

Would be great if we would have a working VVV out of the box.

Happens when we try to download a private file

[Rayken]

Still getting this 'bug'. Plugins that cache files to wp-content/uploads/ and maybe cache/files/* aren't accessible due to this; can't seem to work around it, even commenting the rules in nginx-wp-common.conf

[tlartaud]

Hi @Quaked

You could simply ssh to the VM and navigate to www/wordpress-default/wp-content and create the required symlinks using the standard ln -s command.

You can find for example the script which is provisioning our symlinks (wp-plugins and wp-themes) here : vagrant-config\provision\provision-post.sh. This script is copied to the VM before provisioning it.

I'm not sure sure that it cause a problem without a symlink. Personally, I don't have one for wp-content/uploads. The problem is just that all the files are kept on the VM, and then synced to my computer, but I really don't care about that.

For the nginx-wp-common.conf files problem, don't forget to re-provision the VM after editing the file.

[tlartaud]

@Quaked @vpratfr
We updated the build-env to use VVV2.
They changed the directory structure from /srv/www/wordpress-default/wp-content to /srv/www/wordpress-default/public_html/wp-content.

To update, I think the best way is to

• dump your database
• destroy the VM
• delete vagrant/.vagrant folder
• delete vagrant/www folder
• pull this repo last version
• run . up-vagrant.sh
• update the main wp-config.php file according to this comment
• add your DB dump back, and maybe perform a DB replace from /srv/www/wordpress-default/wp-content to /srv/www/wordpress-default/public_html/wp-content using a DB replacement tool (free), or WPMDB (premium).
• done

For the files issue, you still need to edit the file nginx-wp-common.conf by hand, delete the files rewrite rules, and then re-provision the VM. It's from the VVV repository, and we have no simple and safe way to delete this automatically before the first provisionning.

Regards.