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
'elasticsearch' is not a registered wp command #185
Comments
Hi @alagirirajesh,
This will give you the exact message as the title of this issue - because
Hope that helps |
I am running |
Did you activate ElasticPress? |
Yes, the problem seems to be that I have wordpress in a subdirectory and it can't find WP_CLI to add the elasticpress command to WP_CLI. |
I was having the same problem when running it on a hgv machine, but in that case you have to run
|
I was able to fix this by changing WP_CONTENT_DIR in wp-config file, ./content being the path to your wp-content location. I was using: wp-cli could now find my project and the elasticpress command was added. |
I am trying to install elasticsearch and have following the instructions as much as possible. But i am getting the above error when i am running the command "wp elasticpress index --setup --network-wide".
Also i am using wpmudev's directory plugin uses custom fields. Can you please let me know if the current version of elasticpress supports custom fields.
Please help. As i did not know where to ask for support writing here. if you can answer or direct me to a place where i can get support should be good.
The text was updated successfully, but these errors were encountered: