Sounds to me like someone intentionally broke a plugin so that customers would have to update the one they have and pay the fee in order to get it to work. Maybe that’s not the case but it sure seems like it. Especially when the error was conveniently fixed before 4.3 came out of beta.
