DB-Toolkit 0.3.3 and WP 3.5.2 throw a PHP error on every page

  • Resolved Ken Wienecke

    (@ken-wienecke)


    10 years, 9 months ago

    I installed WP 3.5.2 on my localhost, then installed DB-Toolkit 0.3.3. Every page on WP now have the error message “Notice: Undefined index: interfaces in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/libs/functions.php on line 933”. This problem seems to be preventing all saves of interfaces, so I’m blocked.

    I saw a forum post about this, seemingly saying that the next update to DB-Toolkit would fix this. What’s the time frame for this update?

    http://wordpress.org/extend/plugins/db-toolkit/

Viewing 4 replies - 1 through 4 (of 4 total)
  • overnoise

    (@overnoise)

    10 years, 9 months ago

    It’s notice, not an error!

    Thread Starter Ken Wienecke

    (@ken-wienecke)

    10 years, 9 months ago

    Well, it’s a notice, but other notices are occurring in many of the DB-Toolkit screens. Here’s the one in the “Field Setup” tab: Notice: Undefined variable: Return in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_form/class.php on line 98.

    I was indeed abel to save a little test interface (of the wp_users table, which has 1 entry–me!). Here are all the PHP notices on the view of that interface:

    Notice:Undefined index:ID in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_report/class.php on line 2116

    Notice:Undefined index:user_login in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_report/class.php on line 2116

    Notice:Undefined index:user_pass in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_report/class.php on line 2116

    Notice:Undefined index:user_nicename in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_report/class.php on line 2116

    Notice:Undefined index:user_email in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_report/class.php on line 2116

    Notice:Undefined index:user_url in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_report/class.php on line 2116

    Notice:Undefined index:user_registered in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_report/class.php on line 2116

    Notice:Undefined index:user_activation_key in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_report/class.php on line 2116

    Notice:Undefined index:user_status in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_report/class.php on line 2116

    Notice:Undefined index:display_name in /Applications/xampp/xamppfiles/htdocs/wp/wp-content/plugins/db-toolkit/data_report/class.php on line 2116

    Moreover, the table display shows no record, so I’m guessing these notices means that MySQL requests are failing somehow.

    I have lots of MySQL background and PHP programming background, but no experience whatever with DB-Toolkit.

    I have deleted DB-Toolkit and reinstalled it from scratch…same problem. The rest of my WP localhost installation works fine.

    Mr. Cramer, do you have any ideas for me to pursue? I would really like to use DB-Toolkit. It seems many others are having great success with it, but I don’t have time to try to debug this myself.

    Plugin Author David Cramer

    (@desertsnowman)

    10 years, 9 months ago

    True, Notices are not errors, but I do not like having them. Production code should never attempt to use a variable that has not been defined. Luckily, DBT is not production code 🙂

    When I first built it about 5 years ago it was for another platform, one that had an environment that maintained defined values. When I switched to WordPress, I needed to adapt many many things. As a result there are a lot of cases where values are undefined.
    I am slowly dealing with them.
    The best way to get rid of them is to disable debug in your config. This should be off in a production site anyway.
    Alternately you can stay up to date by getting the dev version of v0.4 on github where some of these problems are resolved
    https://github.com/Desertsnowman/DB-Toolkit

    Thread Starter Ken Wienecke

    (@ken-wienecke)

    10 years, 9 months ago

    Thanks so much for your reply, David. I understand completely.

    Yes, I had debugging on but forgot about it. All those warnings and notices are gone now. My site is not really production, it’s just a localhost site to play with for the purpose of learning DB-Toolkit.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘DB-Toolkit 0.3.3 and WP 3.5.2 throw a PHP error on every page’ is closed to new replies.