Do you even test your versions? 3.2.3 notification cannot be dismissed

Yes. Same behavior here. And this isn’t the first version that’s had this bug.

Ok. I’ll bite. Yes, we tested every single version. Extensively. And on several environments.

Now the return question, have you? Have you tested our release candidates? Have you signed up for our beta mailing list? Have you helped us to make things better?

Well a testy response there.

Personally I would let the changelog answer the question:
3.2.3
Release Date: April 21th, 2016
3.2.2
Release Date: April 21th, 2016
3.2.1
Release Date: April 20th, 2016
3.2.0
Release Date: April 20th, 2016

I have 55 wordpress blogs and I rely on Wordfence to make sure that plugins, core and themes are updated.

To have hundreds of notifications from this plugin has cost the the better part of half a day in pointless updates.

If you have to issue four updates in 4 days, you are NOT testing properly or do not have the resources, end of.

No one forces me to use the free version, but with the amount of screw ups hell would freeze over before I’d pay for the premium version.
Biting a user for expressing frustration really casts you in an unappealing light old bean.

I have the same problem too. I’m running 3.2.3 Yoast and the notification will not go away.

Exactly, premtel you have reason so many consecutive updates do not need to subscribe to the list of beta testers we utilizais users as such and so – you shirk work reviewing the code line by line and solve the problem once and for all understand Taco Verdonschot

It is the ONLY plugin i hesitate to update as numerous updates normally follow the initial release. I,m not a tester, but i’m not a tester of others either yet they don’t get released with so many bugs. The free version should be your gateway to a paid version, but how on earth can we pay for a plugin that is not fully tested and has so many bugs on repeated occasions? Very few posts here get replied to and it feels you folk just don’t care.

Wonderful. Tick the post of as resolved. Run and hide fellas.

Taco you’re Dutch, I thought and expect a better command of English having worked for a Dutch company for 12 years. If you feel the need to comment to an English user of your product it would be better if you asked an English speaking member of your team to do that.

I maintain that the attitude we are seeing here is half the issue.
Sort out the attitude and the product and maybe users will buy your commercial version.

Pile on the sarcasm and snappiness as you have done twice now and it shows more about your inadequacies than your qualities.

I don’t have a dog in this fight, but my take on the Yoast response was that Yoast et al want to toss blame back onto the users for not sub’ing to beta testing. Its a classic technique whereby the victim is to blame for the incident. If the victim only participated in testing Yoasts products for them, the victim would not be a victim. So its the victims fault and responsibility is shifted from creator to user.

Taco should not have done that. Taco should have said “Yep, we test until our fingers are numb, and we hate missing things. Please tell me how we can do better.”