• Hi @hellofromtonya,
    thank you so much to create this useful plugin it really help my dev work and I love the fact that I do not have to config xDebug on my machine.

    Anyway I am writing to you just because I noticed that when I have this plugin activated is impossible to install new plugin via the admin interface (no issue if I install a plugin via WP CLI).

    I get the Undefined property: stdClass::$plugin error message.

    This is not a great issue because we should use the plugin in a dev environment and once we know this bug we just need to deactivate it to install a new plugin via the admin interface.

    Thanks again for all your work!

Viewing 1 replies (of 1 total)
  • Plugin Author Tonya Mork

    (@hellofromtonya)

    Hello Andrea,

    Thank you for letting me know about this problem.

    Thinking out-loud:

    • There’s no variable/property called $plugin in the Debug Toolkit plugin.
    • That said, I’ve seen reports of other packages triggering the same error when adding a UI presentation layer over the admin back-end.
    • The Debug Toolkit includes 3 packages (Kint, VarDumper, and Whoops) that add such a UI presentation layer.
    • It’s possible that any of these packages are not playing nicely in the back-end or may be conflicting with another plugin.

    Let me ask you a couple of questions to help me recreate this problem and get it solved:

    • What’s the PHP and WordPress versions?
    • Are you using any Kint or VarDumper functions in your code? If yes, does the error go away when you remove them?
    • Are there any other notices in your debug log – these might trigger Whoops?
    • Do you have other plugins that are activated? If yes, what are they?

    I appreciate your help sniffing out the root cause of this problem.

    Cheers,
    Tonya

Viewing 1 replies (of 1 total)
  • The topic ‘Cannot install new plugins (Undefined property: stdClass::$plugin)’ is closed to new replies.