• Resolved jenwhitedesign

    (@jenwhitedesign)


    I was recently contacted to help get a website back up and running after the client’s former web company disappeared. The site uses the Aveda theme which came with the All In One SEO plugin. This plugin is causing a front-end php error on the home page only. I have removed the plugin from the site, but the error message remains.

    Warning: Undefined array key “page” in /var/www/wp-content/plugins/aioseoextensions/aioseoextensions.php on line 417

    Another interesting tidbit is that I installed and ran the Health Check plugin, and it shows a plugin called “All in One SEOExtensions”, which is in fact the cause of the error, because it disappears when it’s deactivated via Health Check. But when I’m not troubleshooting via Health Check, that plugin isn’t in the list at all.

    I do not have FTP access to log in and see if the plugin folder still remains there, nor to suppress the front end errors via the wp-config file. Does anyone have an idea how this could possibly still remain when the All In One SE plugin has been deleted and All in One SEOExtensions doesn’t even appear in the plugin list?

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi @jenwhitedesign,

    Thanks for reaching out!

    Could you please share the full error log with us?

    Alternatively, it would be best if you could reach out through our Contact Us form so we can provide more detailed support to resolve this issue effectively.

    Feel free to reach out to us at?https://aioseo.com/contact/.

    Our customer success team will be happy to help you via the contact form on our site.

    Looking forward to helping you.

    Thread Starter jenwhitedesign

    (@jenwhitedesign)

    I was able to get FTP access and sure enough, there was a folder for the All In One SEO plugin that doesn’t appear in the actual plugin list (unless using Health Check Troubleshooting Mode as mentioned above).

    Once that folder was deleted, the error disappeared.

    I’m considering this resolved, but do find it odd that this plugin would be active on the site even though it was not listed in the plugin list.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.