-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WordPress in a subdirectory #72
Comments
+1 This is a good idea to have WordPress core in subdirectory. Specially if your are using version control like |
+1 From me also. Would be great to have support for this. |
+1. @nlemoine I have a similar setup. (I used Mark Jaquith's WP-Skeleton to add Wordpress as a Git submodule.) When I try your method above like this:
The directory it looks for is:
Were you able to get this to work? |
@jasonlmann, sure, it should work this way.
Are you certain that the directory exists? |
I'm having a similar issue when trying to pull DB from remote to local vvv install: I have WP installed on a remote server in a subdirectory called "wp" So the path to wp-content on remote is:
Without setting anything other than the Wordpress path for the remote server in the movefile:
..all plugin, theme, and upload files pulled fine into my vvv setup! BUT pulling the database throws an error:
...because it's looking for the dump file on remote in the wrong place... (disregarding the wp subdirectory). Here's the full error (real paths are changed for this post):
The problem is here:
How come it doesn't look for the dump download in the right place on remote? Thanks for any help with this! |
@onlyskyguy, as I have commented on #228, I had same situation. You can achieve pull -d by setting movefile like: production: And add the following( or your local domain ) to wp-config.php to force setting wp_home option: define( 'WP_HOME', 'http://mywebsite.com' ); |
We consider this resolved. Add these instructions to documentation. |
Hi, a wordpress core push is working perfectly fine wordmove push -e staging -w but none of the wp-content pushes are working. wordmove push -e staging -u gives me:
but in my content/uploads are some files pushing DB gives me this error: local | wp search-replace https://client.local/wp http://dev.client.com/wp --quiet --skip-columns=guid --all-tables --allow-root
Error: This does not seem to be a WordPress installation. last but not least: wordmove doctor gives me following error Validating movefile section: local ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
❌ error | [/paths] key 'paths:' is undefined. anyone can help me? folder structure |-movefile.yml
|-wwwroot
|--content # my custom wp-content folder
|---themes
|---uploads
|---plugins
|--wp # wordpress core folder
|--wp-config.php movefile.yml local:
vhost: https://client.local/wp
wordpress_path: /Users/me/Sites/clients/client/wwwroot/wp
paths:
uploads: ../content/uploads
plugins: ../content/plugins
themes: ../content/themes
staging:
vhost: https://dev.client.com/wp
wordpress_path: /vhosts/domain/subdomains/dev/wwwroot/wp
paths:
uploads: ../content/uploads
plugins: ../content/plugins
themes: ../content/themes wp-config.php define('WP_SITEURL', 'https://client.local/wp');
define('WP_HOME', 'https://client.local'); |
Hi,
I'm using WordPress in a subdirectory and I'm setting my own content, plugins, plugins-mu directories. Here's my folder structure:
Although Wordmove plays nicely with custom directories (with
paths
), it doesn't deal with WordPress in a subdirectory. From what I observed, it takes the WordPress path and adds the custom paths behind. I'm for example ending up with something like:instead of:
As I'm mostly using Wordmove for database migration, it's fine and I can deal with this "issue" by setting paths like:
But it would be nice that Wordmove considers content, plugins, uploads, etc. folders as not necessarily contained by wordpress directory (e.g. sometimes absolute content path isn't wordpress absolute path + content relative path). Maybe by detecting absolute path in
paths
?The text was updated successfully, but these errors were encountered: