• Resolved zadine

    (@zadine)


    I have been getting fatal error emails from my wordpress site and all points to ASE and it’s media replacement feature. Here’s the error message from wordpress mail:

    Error Details
    =============
    An error of type E_ERROR was caused in line 122 of the file /nas/content/live/systam/wp-content/plugins/admin-site-enhancements/classes/class-media-replacement.php. Error message: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, bool given in /nas/content/live/systam/wp-content/plugins/admin-site-enhancements/classes/class-media-replacement.php:122
    Stack trace:
    #0 /nas/content/live/systam/wp-content/plugins/admin-site-enhancements/classes/class-media-replacement.php(122): array_key_exists(‘original_image’, false)
    #1 /nas/content/live/systam/wp-includes/class-wp-hook.php(324): ASENHA\Classes\Media_Replacement->replace_media(28382)
    #2 /nas/content/live/systam/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array)
    #3 /nas/content/live/systam/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #4 /nas/content/live/systam/wp-includes/post.php(5010): do_action(‘edit_attachment’, 28382)
    #5 /nas/content/live/systam/wp-includes/post.php(6580): wp_insert_post(Array, false, true)
    #6 /nas/content/live/systam/wp-includes/post.php(5195): wp_insert_attachment(Array, false, 0, false)
    #7 /nas/content/live/systam/wp-admin/includes/post.php(453): wp_update_post(Array)
    #8 /nas/content/live/systam/wp-admin/post.php(227): edit_post()
    #9 {main}
    thrown

    Fix?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Bowo

    (@qriouslad)

    @zadine thank you for reporting this in detail. Will investigate a fix. By the way, are you aware of when / where the error occurred? In other words, what action triggered the error?

    Thread Starter zadine

    (@zadine)

    no, this is just an automated email from wordpress that site has encountered fatal error.

    Plugin Author Bowo

    (@qriouslad)

    @zadine Got it. This will be fixed in the next release, v8.0.5, scheduled for next Monday. Thanks again for reporting this complete with the error log entry and stack trace.

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

You must be logged in to reply to this topic.