@phasar40 Yes, there was a release issue with versioning. I was just experiencing it myself. We failed to add the correct version number and things got a little twisted trying to fix that in the WordPress repository.
We’re going to need to patch that for a 2.5.17 release, which I’ll push in the next 24 hours.
@phasar40 Okay, deactiveate 2.5.15 and once you do that, you should see an update to 2.5.17. Once you update, that should solve the issue.
Thread Starter
Frank
(@phasar40)
Ok that seems to have fixed it
thanks
@phasar40 Awesome. Sorry for the trouble, but glad it was resolved!