Akismet update

[mrppp]

in beta version keeps wanting to update Akismet

[GregLone]

It's even worse than that: delete Akismet and it will get back by itself a few minutes later.

[Ipstenu]

GregLone - That;s not an issue we're going to fix. Akismet comes with WordPress on upgrades the normal way too.

Now getting it updated in the BETAS would be nice :) And will happen before 4.0 is released.

[GregLone]

Replying to Ipstenu:
Hey, thanks :)
You mean Akismet won't be optional anymore? That's a bit surprising. :|
I already see the next most wanted plugin in the repository: "Get rid of Akismet" =D

[Shapeshifter 3]

I've received notification that Akismet needs to be updated to version 3.0.1 for several days. On 3 sites that I own (all using the current Beta Version of WordPress, that update refuses to work. I tried to disable and then delete the plugin on 2 of the sites, and Akismet was reinstalled on both of them. My current thought is to try replacing Akismet usage with this plugin: ​https://wordpress.org/plugins/zero-spam/ whose author seems to indicate that I will not need to use the Captcha plugin anymore either.

Any thoughts?

[juliobox]

Hello

@mika Are you telling us that even if we delete Akismet, the auto updates will bring it again and again? I hope i'm wrong.

If this is true, i hope that the CORE_UPGRADE_SKIP_NEW_BUNDLED constant will always work, does it?

I don't want a plugin i don't need.

Thanks!

[mrppp]

Yes even if i delete the plugin, it still comes back asking to update it, if i update it it still keeps asking to be updated too

[Ipstenu]

I'm going to try and break this one down for you.

WordPress updates have always included Akismet and the default themes. Auto-updates for major releases will include it, just like they always have. Auto-updates for trunk/nightly/beta are treated as major updates, so yes, that will continue to include it.

Yes, right now Akismet's version included in Core is out of sync. This issue would occur when you reinstalled WP. It's not 'new'.

Akismet reinstalling at all is NOT a bug, it's expected behavior. Akismet being out of sync IS a bug (technically) and will be fixed.

CORE_UPGRADE_SKIP_NEW_BUNDLED should work. If it's not, please make a new ticket for that.

[SergeyBiryukov]

Replying to juliobox:

Are you telling us that even if we delete Akismet, the auto updates will bring it again and again? I hope i'm wrong.

No, if Akismet was deleted, it should not be reinstated on update, see #14484 and [17576].

But that only applies when upgrading to a stable release. Beta releases and nightly builds still include all the bundled plugins and themes, otherwise we wouldn't get updates for bundled themes while they're in development.

[mrppp]

Ok so Beta releases just reinstall the plugin hence keeps appearing, a non beta release would only update core files not the plugin so while updating nightly build i am in effect reinstalling Akismet again each update thanks

[Shapeshifter 3]

So, does this code work, or not:

CORE_UPGRADE_SKIP_NEW_BUNDLED

AND IF SO, can anybody tell me where to place it ?

[GregLone]

Replying to Shapeshifter 3:
In wp-config.php: define( 'CORE_UPGRADE_SKIP_NEW_BUNDLED', true );

[Socially Uncensored]

Unlike everyone here, I WANT Akismet. My problem is everytime WordPress self updates, it overwrites the current installed Akismet.

The problem with this is the bundled installed version is 3.0, yet 3.0.1 has been out for well over a month. So I always have to manually update the Akismet plugin again and again.

Can we please include the latest version (sooner rather than later)?

[nacin]

I've bumped the Akismet external to 3.0.1 in the 3.9 branch and in trunk, and then updated the nightly builds to reflect that. So you should no longer have a problem.

It's by design for bundled stuff to be installed during betas. While we could probably exclude Akismet from this, we sometimes bump trunk to Akismet trunk to allow for a bit of testing. Closing as invalid.

[SergeyBiryukov]

#29263 was marked as a duplicate.

[ocean90]

#29266 was marked as a duplicate.

[SergeyBiryukov]

#50398 was marked as a duplicate.