Support » Plugin: SEO Tools » [Plugin: SEO Tools] Error

  • Resolved AllenPayne


    I get this error because of this plugin:

    Warning: call_user_func_array() []: First argument is expected to be a valid callback, ‘aaa_result’ was given in /home/…../public_html/……/wp-includes/plugin.php on line 170

    This error shows up at the top of the plugins page in my wp admin panel. It doesn’t let me search for new plugins or update existing ones.

    If i deactivate the SEO tools plugin everything works perfectly.

    Any ideas?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Scott Hendison


    This was resolved via email support via, so I am marking it closed. If someone has an issue please post new.

    I still have this problem.

    When i activate the plugin i get this error:

    The plugin generated 281 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

    And when i try to search for new plugins and update existing ones i get this one:

    Warning: call_user_func_array() []: First argument is expected to be a valid callback, ‘aaa_result’ was given in /home/…./public_html/my/wp-includes/plugin.php on line 173

    I’ve been having this problem for almost 6 months.

    Can you post the solution here?

    Plugin Author Scott Hendison


    Hi Allen, I’m a little confused by this:
    “And when i try to search for new plugins and update existing ones i get this one:”

    So are you saying that you cannot search for any new plugins or update existing ones without getting an error, if our plugin is activated? And when it IS activated, there’s a persistent error at the top of your admin panel?

    If that’s the case, then deactivate and delete our whole plugin folder entirely from your /plugins folder (i prefer FTP), and then try to install a new version.

    If the problem persists, then there must be some conflict with some other plugin on your site, and a methodical disabling / enabling of the others would be necessary to track it down.

    If you can do the legwork to determine which plugin we may be in conflict with, we’ll take a look and see if it should be fixed on our end….

    Typically, I think it’s the responsibility of the less popular of two conflicting plugins to ensure compatibility – for example, if we conflict with a popular plugin with half a million downloads, and we have only 50,000 users, then it’s on us.

    Please post back here further, and I’ll also ask Heather (dzynit) to chime in in case she has any ideas…

    Plugin Author Dzynit


    The headers already sent message is most commonly a plugin conflict or when the plugin files corrupted during installation. I occasionally have a problem where the plugin files didn’t fully unpack and install correctly because the server had suddenly gone down at the time of installation.

    Scott’s suggestions are best to try first. Deactivate seo tools, fully delete it and try installing it fresh first to see if there was a corruption during installation. If the error persists, as tedious as it may be – turning off all your active plugins, activate seo tools first, and one by one reactivate all your others, each time testing a new plugin search to see when you get that second error.

    Since it really wouldn’t take much time, if you want to send me a zip of only your active plugins, I can put them on a test site simply to confirm it being the plugins and not a possible server configuration. I don’t currently have available time to test for which plugin is the conflict, but can at least help to confirm that it definitely is a conflict. You can send the zip to heather(at) if you want me to do that.

    Plugin Author Scott Hendison


    No zip was ever sent, and we can only do so much without help from the site owner, so I’m marking this as resolved. @allenpayne feel free to post here again and reopen the ticket…

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: SEO Tools] Error’ is closed to new replies.