This message is likely to be removed in a future version. This causes too much confusion than help, and this is not entirely necessary. Yes, it would be helpful if the development magazine tells you which addon is causing the problem, but the logistics of parsing backtracks to find this information is difficult. This leads us to message # 2:
As GDmac said, it is best to look for your project for any login_form () calls in the CP controller. Usually a file and line number is provided in this type of message, but, as I said, analyzing backtrace information does not always work.
We will continue to try to make it better. Obsolete warnings work fine for the most part, but sometimes messages like these can be hard to figure out what to do with them.
Kevin cupp
source share