It was not really an error, only a warning that the entry was keeping the behavior from 7.22 and earlier. And you can keep it like that or make the decision to swap to the new 7.23 behavior (that will then remove the warning). See the discussion at the end of this RC thread