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

Plugin (de)activation doesn't work correctly with object cache #1078

Closed
Rarst opened this Issue Mar 20, 2014 · 5 comments

Comments

2 participants
@Rarst
Contributor

Rarst commented Mar 20, 2014

Local install with APC object cache. Using wp plugin activate / wp_plugin_deactivate reports "Success" status and wp-cli sees plugins array changed (wp option get active_plugins).

However actual WP install doesn't — plugin status doesn't change in interface and even gets "stuck", trying to perform activate/deactivate in interface on the plugin doesn't work properly anymore and requires flushing cache.

@scribu

This comment has been minimized.

Show comment
Hide comment
@scribu

scribu Mar 20, 2014

Member

trying to perform activate/deactivate in interface on the plugin doesn't work properly anymore and requires flushing cache.

Shouldn't this be fixed in Core first? Is there a ticket?

Member

scribu commented Mar 20, 2014

trying to perform activate/deactivate in interface on the plugin doesn't work properly anymore and requires flushing cache.

Shouldn't this be fixed in Core first? Is there a ticket?

@scribu

This comment has been minimized.

Show comment
Hide comment
@scribu

scribu Mar 20, 2014

Member

Or you mean it works fine via wp-admin, until after you run wp plugin deactivate?

Member

scribu commented Mar 20, 2014

Or you mean it works fine via wp-admin, until after you run wp plugin deactivate?

@scribu scribu removed the scope:command label Mar 20, 2014

@Rarst

This comment has been minimized.

Show comment
Hide comment
@Rarst

Rarst Mar 20, 2014

Contributor

Yes. It works fine in interface before trying to use wp-cli. It seems wp-cli makes database value out of sync with cache value or something like.

Contributor

Rarst commented Mar 20, 2014

Yes. It works fine in interface before trying to use wp-cli. It seems wp-cli makes database value out of sync with cache value or something like.

@scribu

This comment has been minimized.

Show comment
Hide comment
@scribu

scribu Mar 20, 2014

Member

I see. This seems like a duplicate of #283, which means that any WP-CLI command that alters the database will cause the cache to get out of sync.

Member

scribu commented Mar 20, 2014

I see. This seems like a duplicate of #283, which means that any WP-CLI command that alters the database will cause the cache to get out of sync.

@scribu scribu added the bug label Mar 20, 2014

@Rarst

This comment has been minimized.

Show comment
Hide comment
@Rarst

Rarst Mar 20, 2014

Contributor

Yeah, that's probably it. Closing in favor of discussion on underlying issue there.

Contributor

Rarst commented Mar 20, 2014

Yeah, that's probably it. Closing in favor of discussion on underlying issue there.

@Rarst Rarst closed this Mar 20, 2014

@scribu scribu added duplicate and removed bug labels Mar 20, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment