I believe that was being logged as deprecated in V3.4 to warn you to fix it prior to the upgrade. If the warning wasn't appearing, that would be a bug (too late to do anything about it, but a bug nonetheless). I don't really know what your question is. -- Scott