I have seen that page before, but it can't hurt to go through and double-check all of those settings for correctness. We already discovered that the db had a default latin1 encoding and are in the process of rebuilding it as utf8mb4, but there might be something else there that's also been missed.