: 1. Why the problem occurs (has something changed between 1.4.1 and 3x)?
Various pieces of code dealing with config parsing have changed since 1.4.1 to be better about verifying that configs are meaningful ,ad reporting errors when unexpected things are encountered. i'm not sure of the specific change, but the underlying point is: if 1.4.1 wasn't giving you an error for that syntax, it's because it was compleltey ignoring it. -Hoss
