-
Notifications
You must be signed in to change notification settings - Fork 20
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
Cannot be installed with wp-cli 2.2.0 out of the box #118
Comments
Of course, see https://github.com/diggy/polylang-cli/blob/master/composer.json#L21 This project may need to wake up. @diggy What do you think? |
@ratzrattillo @szepeviktor I've been out of the WP ecosystem for a while, but it looks like I might be circling back over the course of the next few months. In the meantime, happy to accept pull requests! |
@szepeviktor @diggy |
Hmm, I don't really understand @szepeviktor solution. In any case, I'm seeing the same error message when using 2.4.0. How can I fix this? |
@diggy could you perhaps elaborate on @szepeviktor solution? |
I've wrote only this, no solution.
I totally don't understand it. |
gotcha @szepeviktor I guess @ratzrattillo had us both confused :) |
Just have @diggy merge it! |
https://packagist.org/packages/szepeviktor/phpstan-wordpress may help you find and fix hidden bugs |
Have you guys found a solution/workaround? |
So is it possible to install it and use with WP CLI in version 2.X.X ? Anyone succeeded with it? |
Ping @diggy |
Hey there,
i would like to try out your very promising package, as the developers of polylang obviously do not yet have any interest in providing a CLI interface.
However when trying to install the pakcage, i get the following errors:
Do you know how to fix this, so the future users can enjoy your tool even with the newest version of wp-cli?
Did you ever think about submitting your polylang-cli project to the official polylang project? I think this would be really useful and maybe they would take over the maintenance for you also .:)
Greetings!
The text was updated successfully, but these errors were encountered: