• Resolved QUEERmdb

    (@queermdb)


    Your update from today crashed my backend. I needed to delete it via FTP.

    Internal Server Error: The server encountered an internal error or misconfiguration and was unable to complete your request.
    Please contact the server administrator at [no address given] to inform them of the time this error occurred, and the actions you performed just before this error.


    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 17179739024 bytes) in **/wp-content/plugins/broken-link-checker/legacy/includes/screen-options/screen-options.php on line 282

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Kris – WPMU DEV Support

    (@wpmudevsupport13)

    Hi @queermdb

    I hope you are doing well today.

    When it comes to error and part about missing memory sounds ridiculously. It seems update required over 17 000 MB. In most cases such errors (in general for all plugins) reports memory around 2MB or 50MB, depend from case, but not thousands.

    Something is not right for sure, as those values seem to be incorrect. There is a high possibility of some sort of conflict, corrupted database, or infinite loop.

    Are you able to create a staging site, to not affect the live site again, and install the previous version of BLC from here:
    https://www.ads-software.com/plugins/broken-link-checker/advanced/

    and run update once more to see does the same issue will happen?

    Also before that, on that staging site, add this code to wp-config.php file:
    define('WP_MEMORY_LIMIT', '512M');

    This define should be placed above the “/* That’s all, stop editing! Happy blogging. */”

    Kind Regards,
    Kris

    Thread Starter QUEERmdb

    (@queermdb)

    Hej Kris, I increased WP MEMORY LIMIT from 256 to 512 MB, activated your plugin again and was able to roll it back to 2.2.1. It works without problems, so I take this as an interim solution. Greetz from Berlin — Johannes

    Hi @queermdb,

    Hope this message finds you well and thanks for the update.

    Glad to hear you were able to fix it.

    Would you let us know if we can mark this as solved, please? Thank you.

    Kind regards,
    Laura

    Thread Starter QUEERmdb

    (@queermdb)

    “Solved” in a way I described above.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘New update cause troubles’ is closed to new replies.