Document alternative solution about polylang-cli HOT 5 CLOSED

See https://github.com/diggy/polylang-cli/blob/master/src/Commands/BaseCommand.php#L12

Also note https://github.com/diggy/polylang-cli/blob/master/src/Commands/Post.php#L225

Why would mentioning this in the polylang-cli documentation be useful or relevant?

from polylang-cli.

Projects usually have an "Alternatives" section in the readme.

from polylang-cli.

@szepeviktor I've been thinking about this, and I'm not convinced this is a viable, alternative solution. Defining the constants is simply not enough; wp post list might work, but for other pll commands I was hoping simply passing args and assoc args to the core command counterparts would suffice, but it does not, take a look at these commands I just implemented:

• https://github.com/diggy/polylang-cli/blob/master/src/Commands/Term.php#L344
• https://github.com/diggy/polylang-cli/blob/master/src/Commands/Post.php#L192

from polylang-cli.

Ok-Ok.
Finding those constants to make wp post * work took me a long time. I thought it worth sharing.

from polylang-cli.

Instead of alternative solution I would call it Viktor's hack:
https://github.com/szepeviktor/wordpress-plugin-construction/tree/master/wp-cli-commands/wp-cli-polylang-enabler-hack

from polylang-cli.