Support » Plugin: Debug This » Shortcode – Critical Error

  • Resolved frgtech

    (@frgtech)


    I need to troubleshoot a shortcode, but it gives me a critical error very quickly.

    14:52:39 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 206573568 bytes) in /home1/friscoro/public_html/fishingreport/wp-content/plugins/debug-this/inc/extensions.php on line 350
    [19-May-2021 14:53:02 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 174067712 bytes) in /home1/friscoro/public_html/fishingreport/wp-content/plugins/debug-this/inc/extensions.php on line 350

    I’ve added a statement to my wp-config, but it didn’t help
    define( 'WP_MAX_MEMORY_LIMIT' , '512M' );

    If you press the top level “Debug This” button on the page preview, it gives you a page layout of all the elements. The shortcode I’m using does not show on that page at all even though I have 2 blocks with the same shortcode. A Shortcode block, and a Custom HTML block. Both just render the actual shortcode text on the preview page, but there is nothing when viewing it with Debug This.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support mplusb

    (@mplusb)

    Hi @frgtech,

    Thanks for reaching out!
    can you please let me know what plugin/shortcode are you trying to troubleshoot?

    Thank you!
    Mihaela

    Thread Starter frgtech

    (@frgtech)

    Hi,
    I actually was able to get the shortcode working. It’s old and unmaintained, but it still works.

    Product Display for BigCommerce

    So even with it working properly, if I run your plugin I still get the critical error.

    Thank you so much for explaining!

    I went ahead and opened a ticket regarding this.
    You can follow the progress here: https://github.com/WPChill/debug-this/issues/5
    We will do our best to solve it in a next update.

    Thank you for your patience and understanding!

    Warmly,
    Beatrice.

    Plugin Support mplusb

    (@mplusb)

    This topic will be marked as resolved as we have an open ticket on GitHub regarding this. Please keep in mind that the ‘resolved’ status is only for this support thread, not the issue on GitHub.

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