Support » Plugin: Debug Toolkit » Debug Toolkit Crashes Formidable Forms

  • This might be an edge case, but the new plugin is crashing while debugging a plugin I’m writing for Formidable Forms. The plugin is designed to write form data to flat tables for better reporting. Acceptable fields receive a “save to db” checkbox in their options.

    The stand alone kint debugger still works fine. But with either plugin loaded, the form stops loading after an error.

    The debug toolkit plugin displays 1 whoops error that has nothing to do with this form. The php error log is showing that an array value is not being initialized properly. Old school PHP debugging works fine though.

    I’m not even sure how you can check this unless you use Formidable and I can send you my plugin.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Clifford Paulick

    (@cliffpaulick)

    Which version of WordPress and PHP are you using? Are you using latest version of Formidable?

    What’s the actual (irrelevant) error?

    Thread Starter Victor Font

    (@vfontj)

    WordPress 5.1.1
    PHP 7.1.23

    Yes, to latest Formidable.

    I suspect that the issue is probably related to the fact that this version of Kint displays on the bottom of the screen. Formidable runs a many loops to display its content. With the standalone Kint plugin, you can place a d() in the middle of a loop and see the output exactly where it outputs as many times as it executes.

    The new location isn’t useful. Whoops only shows as a single line of text, and when something finally does display, the entire screen has been turned into a multi-column display instead of a normal looking screen.

    My dev environment is local on my Mac using the native Apache and PHP installed with Mohave. I had to revert back to the stand alone Kint to get my development work done.

    Clifford Paulick

    (@cliffpaulick)

    That should be enough for @hellofromtonya to run with…

    Plugin Author Tonya Mork

    (@hellofromtonya)

    Hello @vfontj,

    Sorry for the late response. And thank you for the extra information to help me sort this out for you. If don’t mind, let me ask a few additional questions.

    All of the questions I’ll ask are to help me investigate, find the root cause, and formulate a solution strategy. Victor, thank you for helping me with this.

    The stand alone kint debugger still works fine. But with either plugin loaded, the form stops loading after an error.

    1. “But with either plugin loaded” – To clarify, if an error occurs, the form does not load with either the Kint Debugger and Debug Toolkit plugins. Is that correct?
    2. When this happens, what function are you using from Kint?
    3. Without either debugging plugin, does the form load with an error?
    4. What kind of error are you getting: notice, warning, or fatal error?
    5. What is the error?

    The debug toolkit plugin displays 1 whoops error that has nothing to do with this form. The php error log is showing that an array value is not being initialized properly. Old school PHP debugging works fine though.

    It sounds like there’s some competing styling happening. Let’s talk about it.

    Variable Inspection:
    The new version of Kint gathers up all of the rendering and displays it at a fixed position at the bottom of the screen.

    Action: Switch to using vdump() instead instead of d(). Notice that vdump() renders where the content would appear. Does this give you the information and debug experience you want and need when working with Formidable Forms?

    How about Whoops?
    Whoops attempts to overlays the entire screen to provide you with detailed information and help for a notice, warning, and fatal error. From what you are describing, it the form and/or something else is competing for the same top-level view.

    My Action: Thank you for reporting this edge case. Currently, I’m not modifying the out-of-box experience with Kint or Whoops. But for Whoops, it seems we need a way to (1) disable it if you don’t want it and (2) handle the top-level display competition.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Debug Toolkit Crashes Formidable Forms’ is closed to new replies.