Manage: Remove Plugin Update Card

[kraftbj]

With Core adding this functionality, until our backup/restore integrations are in place, we should remove this card to avoid confusion.

Steps to reproduce the issue

n/a

What I expected

n/a

What happened instead

n/a

[dereksmart]

When we look into this, let's also consider the one on the main dashboard

[pablinos]

I'd missed this feature being merged. Perhaps we could check for the presence of wp_is_auto_update_enabled_for_type and use that to determine whether to disable this UI?

[jeherve]

Perhaps we could check for the presence of wp_is_auto_update_enabled_for_type and use that to determine whether to disable this UI?

Since that's a Core feature now, I'd be tempted to not mention the feature at all in the Jetpack dashboard, at least not until we've made some improvements to our implementation so it's better than Core's.

[pablinos]

That makes sense. I suppose I was thinking about people that were on < WP 5.5, but then any change would be in a new version of Jetpack they would need to update to also.

[allilevine]

Since that's a Core feature now, I'd be tempted to not mention the feature at all in the Jetpack dashboard, at least not until we've made some improvements to our implementation so it's better than Core's.

Should we hide the feature from the dashboard (e.g. with a feature/config flag)? Or remove it from the code entirely since it will be implemented differently if it comes back?

[jeherve]

I think it'd be safe to remove entirely. We can always pull the code back if needed later on.