Since the warning is issued in a core file and not within the plugin, there might be some sort of incompatibility I'm not aware of, but it might come down to the implementation. Did you make the additional updates to your theme files to accommodate version 3?
↧
