Updating to 4.1.1 from 4.1.0.2 causing issues

  • Resolved Jon Fuller

    (@garconis)


    3 years, 6 months ago

    When updating to 4.1.1 on my Cloudways site, I’m getting a “504 Gateway Time-out” after a couple minutes. So I deleted from SFTP, and then re-installed the plugin. Upon “Activation” of the plugin, I get “504 Gateway Time-out” again.

    I then go back to wp-admin and check the plugin area, and the AIOSEO plugin is there but not activated. Has something changed? What would be causing these issues? I had updated to 4.1.0.2 just fine a couple days ago.

    Apache error logs are saying stuff like:

    [Thu May 20 16:20:48.044641 2021] [proxy_fcgi:error] [pid 11232:tid 139762513958656] [client 108.183.39.217:39300] AH01071: Got error 'PHP message: PHP Warning: Invalid argument supplied for foreach() in /home/XXX.cloudwaysapps.com/asdfsfsdfsd/pub..............aximum execution time of 120 seconds exceeded in /home/XXX.cloudwaysapps.com/asdfsfsdfsd/public_html/wp-content/plugins/_all-in-one-seo-pack/app/Common/Utils/Options.php on line 492', referer: https://www.mytestsite.com/wp-admin/plugins.php?
[Thu May 20 16:45:00.831443 2021] [proxy_fcgi:error] [pid 2356:tid 139762127894272] [client 108.183.39.217:41286] AH01071: Got error 'PHP message: PHP Warning: Invalid argument supplied for foreach() in /home/XXX.cloudwaysapps.com/asdfsfsdfsd/publ..............home/XXX.cloudwaysapps.com/asdfsfsdfsd/public_html/wp-content/plugins/all-in-one-seo-pack/app/Common/Traits/Options.php on line 899', referer: https://www.mytestsite.com/wp-admin/plugin-install.php?s=all%20in%20one%20seo&tab=search&type=term
[Thu May 20 16:46:01.555608 2021] [proxy_fcgi:error] [pid 2356:tid 139762085930752] [client 108.183.39.217:41350] AH01071: Got error 'PHP message: PHP Warning: Invalid argument supplied for foreach() in /home/XXX.cloudwaysapps.com/asdfsfsdfsd/publ............../home/XXX.cloudwaysapps.com/asdfsfsdfsd/public_html/wp-content/plugins/all-in-one-seo-pack/app/Common/Utils/Options.php on line 492', referer: https://www.mytestsite.com/wp-admin/plugin-install.php?s=all%20in%20one%20seo&tab=search&type=term

    The hosting provider (Cloudways) said:

    I got the same error on command line while activating the plugin. It says plugin already activated but on dashboard it does not activated.

    I then tried deleting the (inactive) plugin from the plugin page, and it wouldn’t even delete. It just say there as “Deleting…” and eventually had this error: https://i.imgur.com/yMYaFc1.png … so I had to get them to help me manually remove the plugin.

    Edit: I was able to install/activate the previous version (4.1.0.2) without any issues.

    • This topic was modified 3 years, 6 months ago by Jon Fuller.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author arnaudbroes

    (@arnaudbroes)

    Hey @garconis,

    Thank you for reporting this.

    This is a strange issue because the line numbers don’t match with what’s in the latest update. I also can’t reproduce it.

    Can you try updating once more and see what happens? I’d connect to your site via SFTP so that you can rename or delete the plugin folder immediately in case you see the same errors.

    Because the update times out, it is possible that some of the files are being corrupted. If it happens again, can you contact us at https://aioseo.com/contact/? You can click the “Complete a Form” button on that page and ask for me.

    – Arnaud

    Plugin Support Steve M

    (@wpsmort)

    Hi @garconis,

    We have now released version 4.1.1.1 of All in One SEO which fixes an issue with updating the plugin affecting some users.

    Please update to version 4.1.1.1 and let us know if you still have any problems.

    • This reply was modified 3 years, 6 months ago by Steve M.
    Thread Starter Jon Fuller

    (@garconis)

    Thanks, that version worked. ??

    Plugin Author arnaudbroes

    (@arnaudbroes)

    @garconis Awesome, thanks for your patience, Jon. It was a rather niche issue, which is why it didn’t come up during our testing.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Updating to 4.1.1 from 4.1.0.2 causing issues’ is closed to new replies.