• Hi, since I upgraded to WordPress 7.0 and I use updated PHP version on all server so PHP 8.5 I get plugin update errors when the auto update is active. I get the fail email error while just some plugin are correctly auto update. I need log in and update manually.

    Different hosting, same WordPress and PHP.

    This issue seems has been introduced with the new WordPress update.
    Any solution? How to understand why this happen?

    Thank you.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hello,

    Possible for you to let us know which specific plugin is failing to auto-update? As I find it bit weird that auto-updates work fine for most plugins but fail for a specific one. There may be the case where a plugin has a premium license connection issue, or the plugin hasn’t quite caught up with the WP 7.0 requirements.

    Any extra details or a screenshot of the error would be helpful.

    Thread Starter peopleinside

    (@peopleinside)

    Hi, thank you for the reply.
    The error is just the notification email that say the following plugin has not been updated.

    There are different plugins indicated in the email and this email is getting delivered since weeks also after updating manually new update has issue. Not all. To me seems an issue introduced by WordPress core update.

    An example of plugins: Yoast SEO, wpDiscuz, PublishPress, Forminator.

    Is not an issue with the plugin is WordPress that are now giving errors and is not just one server is from different hosting type of servers.

    Moderator threadi

    (@threadi)

    There can be many reasons for a failed update. Some of them should be listed in the hosting error log. Have you checked there? Pay attention to the time the email was sent and any entries in the log around that time.

    Thread Starter peopleinside

    (@peopleinside)

    Thank you for the reply.
    I checked server error log and I cannot find anything at the email alert time.

    Also sound strange to me websites from different hosting and different server are having this issue.

    Hi @peopleinside,

    Can you try enabling debug mode and see if there are any errors generated in the debug.log file, which could give further clues on what might be causing it?

    Please check this link for more info about enabling debug mode:
    https://learn.ww.wp.xz.cn/tutorial/debugging-in-wordpress/

    In short, once you enable debug mode, you’ll need to reproduce the issue for the error to occur. Once the error occurs, the related logs will be saved to the debug.log file, where the file content will mention what exactly is causing the issue.

    The error inside the debug.log file should provide a clearer indication of whether it’s a plugin-related issue, etc. This would help in moving in the right direction.

    Regards,

    Nithin

    Thread Starter peopleinside

    (@peopleinside)

    I will try also if I think this issue has introduced with WordPress update as I never had and never seen this before. Thank you!

    Hi @peopleinside,

    It is also worth trying to reinstall the WordPress core and see if that helps to resolve the issue. If the issue persists, try downgrading the WordPress core and see if that resolves the issue.

    Best Regards,
    Nebu John

Viewing 7 replies - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.