@sumitsanadhya, yes, if I add the extra define, then it removes the error for us. This is not default with the version of WordPress (latest). Is there any further update on how to resolve this? It sounds like 4.1.6 worked, so will you revert the code to the old behavior or are we forced to add this new define to our config file?
