OK… You helped me isolate the ‘plugin’ that was throwing that error. It was one designed to allow a person to log in with their email called WP Email Login. I deactivated it and verified that that error is gone. Since the benefit outweighs the non-destructive error…I will probably reactivate it.
Now…the other plugin… AG Custom Admin… This plugin is designed to allow me to “white label” the wordpress site. It’s supposed to allow me to customize what is available in the “backend” to my “customer” who will need to make posts and such.
There is another plugin…more limited though…that will “white label” as well, but the customization is less.
I definitely prefer AG Custom Admin – unless there’s one I’m unfamiliar with…. since I can actually “hide” certain fields within the post creation area… so they don’t inadvertently click check marks they shouldn’t…
But…when AG Custom Admin is active…the login button (in SP) is dead…
Thanks so much!