• Resolved Norm Sash

    (@normsash)


    Hi, I just tried installing the plugin and added the do_action line. But when I’m on the front-end I get the error

    WordPress database error: [Table 'atter_stage61.wp_variable_inspector' doesn't exist]
    SHOW FULL COLUMNS FROM wp_variable_inspector

    I uninstalled and reinstalled but it seems like the required table isn’t created. Is there something I’m doing wrong?

    Thanks,

    -Norm

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

    (@qriouslad)

    @normsash Thank you for reporting the issue. Can you check with SQL Buddy plugin if the table has been created or not? If it’s been created, please take a screenshot and share via imagebam[dot]com or a similar service.

    Another question: what type of hosting or service did you use to try out VI? I notice the table name is rather unusual ‘atter_stage61.wp_variable_inspector’ with the atter_stage61 prefix. Shouldn’t be a problem, but maybe there’s a clue there.

    I just tried installing VI on a fresh WP 6.2.2 / PHP 8.1 install in InstaWP and the table is being created just fine.

    • This reply was modified 1 year, 8 months ago by Bowo.
    Thread Starter Norm Sash

    (@normsash)

    Hi, and thank you for the response. I just reactivated it again and then checked for the table wp_variable_inspector but didn’t find it.

    As to the name ?‘atter_stage61.wp_variable_inspector’, the ‘atter_stage61’ is just the prefix for the database name. Actually, it’s cut off at the beginning just because I shortened it, but still, it’s just the database name.

    Here’s a screenshot of the tables showing it missing (sorted alphabetically)…

    Plugin Author Bowo

    (@qriouslad)

    Hmm… strange… could you install Debug Log Manager plugin, another one of my plugins, enable debugging with it. And then deactivate and reactivate Variable Inspector again, and see if there are any errors logged.

    The other odd thing os, SQL Buddy should be showing the ‘atter_stage61.’ prefix as well, but it s not.

    Can you give any info on your hosting / server set up?… especially how new sites and DBs are created there?

    Plugin Author Bowo

    (@qriouslad)

    Hmm… strange… could you install Debug Log Manager plugin, another one of my plugins, enable debugging with it. And then deactivate and reactivate Variable Inspector again, and see if there are any errors logged.

    The other odd thing os, SQL Buddy should be showing the ‘atter_stage61.’ prefix as well, but it s not.

    Can you give any info on your hosting / server set up?… especially how new sites and DBs are created there?

    Thread Starter Norm Sash

    (@normsash)

    In Debug Log Manager I got the following error when trying to activate Variable Inspector:

    You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 13 for query CREATE TABLE wp_variable_inspector ( ID int(11) unsigned NOT NULL auto_increment, category varchar(255) NOT NULL default '', type varchar(10) NOT NULL default '', name varchar(255) NOT NULL default '', content longtext NULL default '', file_path varchar(255) NOT NULL default '', line_number varchar(11) NOT NULL default '', extra varchar(255) NOT NULL default '', date datetime NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (ID) ) DEFAULT CHARACTER SET utf8 COLLATE made by activate_plugin, do_action('activate_variable-inspector/variable-inspector.php'), WP_Hook->do_action, WP_Hook->apply_filters, activate_variable_inspector, Variable_Inspector_Activator::activate, dbDelta

    I’m running PHP Version 7.4.33 and Maria 10.5.21

    The server is a Litespeed server, shared hosting. Nothing special in terms of managing it… I just use cPanel + Softaculous to install WordPress.

    Let me know if you need anything else.

    Plugin Author Bowo

    (@qriouslad)

    @normsash that’s great info.Thank you. Will investigate a fix for the next release.

    Plugin Author Bowo

    (@qriouslad)

    This has been fixed in v2.5.1. Marking as resolved.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Database error ‘wp_variable_inspector’’ is closed to new replies.