Repository navigation
Asynchronous Plugin installation #29
Description
Activity
Thanks for the report @moshie.
I don't believe this is a fixable problem but I welcome suggestions otherwise. If you install plugins asynchronously, you'll have two separate, parallel processes using the object cache and writing to the database. You can read more about the nature of the problem here: https://core.trac.wordpress.org/ticket/31245
@danielbachhuber Thanks for getting back so quickly and the link to the ticket!
I was afraid that might be the case. Could explain why WordPress only updates it's plugins one at a time even when attempted with ajax.
I am not overly familiar with the inner workings of wp-cli I only stumbled on this as I am building a node api wrapper for wp-cli and was hoping to be able to spawn async child processes for plugin & theme installation.
Could explain why WordPress only installs it's plugins one at a time even when attempted with ajax.
Exactly.
I am not overly familiar with the inner workings of wp-cli
Under the hood, WP-CLI simply wraps WordPress core functions. It's typically outside the scope of the WP-CLI project to solve issues in WordPress core.
I am building a node api wrapper for wp-cli
Neat!
was hoping to be able to spawn async child processes for plugin & theme installation.
Probably safest to avoid async for now and instead batch installation whenever possible (e.g. wp plugin install <plugin>...)
@danielbachhuber I know this is an old topic and slightly off-topic, but releated, could it be possible to run commands "asynchronously" in remote alias groups.
For example, updating the plugins for a WP-CLI alias group @live-sites, containing a 100 sites, but not have it done sequentially to save time.
wp @live-sites plugin update --all
@theodejager Want to open a new issue for that in the main repo? https://github.com/wp-cli/wp-cli/issues
Thanks @danielbachhuber, I opened a new issue!
When attempting to install plugins Asynchronously using the bash
&WP-cli throws errors regarding failed plugin installation.To recreate this issue run these commands on a fresh WordPress install.
Log: