Theme folder path not updated with cap deploy.

[roots]

Theme folder path not updated with cap deploy.

[swalkinshaw]

This is a bit confusing to me. Can you share an example of what your theme is before/after? Do you mean the path in wp_options table somewhere?

[theantichris]

It is the default Twenty Fourteen theme right now. I just switch it to another theme then back and it fixes.

Specifically it looks like the template_root option in the wp_options table is not be updated after a deploy. It is still pointing to the previous release in the releases folder.

[swalkinshaw]

Are you using Apache or Nginx?

[theantichris]

Nginx.

[swalkinshaw]

Interesting that this hasn't come up before. WP does some complicated stuff to do with theme and template directories. It seems like this is only triggered if you have multiple theme directories (which Bedrock does by default). I always remove https://github.com/roots/bedrock/blob/master/web/app/mu-plugins/register-theme-directory.php which means this wouldn't happen.

See here for example: https://github.com/WordPress/WordPress/blob/666fec5144eb3f7df7ee08e345a2e11db4d292ee/wp-includes/theme.php#L604-L627

This will probably take more debugging. One interim solution would be to include a WP-CLI command during the cap deploy process.

Something like:

namespace :deploy do
  task :update_options do
    on roles(:app) do
      within fetch(:current_path) do
        execute :wp, :option, :set, fetch(:release_path).join('subdir/to/themes')
      end
    end
  end
end

after 'deploy:publishing', 'update_options'

[theantichris]

Thanks for looking into this.

I tried the wp-cli stuff but it kept telling me "Error: This does not seem to be a WordPress install." even with the yml file there or specifying the path on the command.

I can hold tight with just switching themes until a solution is found.

[swalkinshaw]

That's because I was missing the within block so it wasn't running in that directory to pick up the wp.yml file. Try again with the edited code above.

[theantichris]

Thanks. I just removed the plugin file since I don't need multiple theme directories. That has me fixed for now.

[liviucmg]

The solution posted by @swalkinshaw worked for me with just a minor change. The "current_path" variable is empty for some reason, so I've replaced it with "release_path". The following code works on Capistrano 3.2.1 and WordPress 4.0 when deployed to Ubuntu 14.04 + Nginx + PHP-FPM (though the deploy target shouldn't really matter):

namespace :deploy do
  desc 'Update WordPress theme path to the new release'
  task :update_options do
    on roles(:app) do
      within fetch(:release_path) do
        execute :wp, :option, :set, :template_root, fetch(:release_path).join('web/wp/wp-content/themes')
      end
    end
  end
end

Note that this requires WP-CLI installed on the server. I'll be making a pull request, since the issue is present on all of my websites. Strange that it appeared fairly recently. Maybe a recent WordPress update caused it?

[grahamharper]

I was getting the white screen of death too but the fix proposed @liviucmg and @swalkinshaw didn't fix this issue for me because I noticed the stylesheet_root wasn't being updated either. I added a new execute line to update this too.

namespace :deploy do
  desc 'Update WordPress theme path to the new release'
  task :update_options do
    on roles(:app) do
      within fetch(:release_path) do
        execute :wp, :option, :set, :template_root, fetch(:release_path).join('web/wp/wp-content/themes')
        execute :wp, :option, :set, :stylesheet_root, fetch(:release_path).join('web/wp/wp-content/themes')
      end
    end
  end
end

[swalkinshaw]

@grahamharper see my other solution here: #101 (comment)

[grahamharper]

Gah, sorry, just saw that now. Cheers. At least the comment might be useful for other folks.