[Guardian Hope]

Originally Posted by vBWonders

Looks like you tried MANY TIMES to run the installation script, Which is wrong, Believe me you are really have the vbwonders_page table in your database !!!

You just need now to import the XML files, Why you keep trying to run the installation script more and more!

Just import the xml file now from admincp and I'll be online until you finish your installation .... Or you can PM me and I can install it for you.

Actually, I executed a search of the database (which mind you, was never touched by this installation script as I dumped it and uploaded the last known good configuration version that I made prior) and guess what: the tables don't exist.

But you know, I went against my judgement about fault and did what you said and imported the XML to finish the installation. Do you know what happened? Database error. The same database error as the first time in fact.

Atop the database error page was this:

Warning: mysqli_query(): (42S02/1146): Table 'databasenameremoved.dbprefixremoved_vbwonders_settings' doesn't exist in ..../includes/class_core.php on line 1393

Now for the actual database error:

Database error in vBulletin 4.2.2:

Invalid SQL:
SELECT vbwonders_value FROM dbprefixremoved_vbwonders_settings WHERE vbwonders_name = 'vbwonders_guard' LIMIT 1;

MySQL Error   : Table 'databasenameremoved.dbprefixremoved_vbwonders_settings' doesn't exist
Error Number  : 1146
Request Date  : Friday, June 12th 2015 @ 09:01:28 AM
Error Date    : Friday, June 12th 2015 @ 09:01:28 AM
Script        : http://domainremoved/forums/adminpathremoved/plugin.php?do=product
Referrer      : http://domainremoved/forums/adminpathremoved/index.php?do=nav
IP Address    : [IP Removed]
Username      : [Username Removed]
Classname     : vB_Database_MySQLi
MySQL Version : 5.5.40-MariaDB-cll-lve

This happens the very moment I import the XML Product after the installer of your newly uploaded version completes.

So now I will spend the five seconds it takes to dump the database again and restore back to the previous configuration.

Considering I'm not the only one having issues with the modification I am going to stand my ground on this one: this modification is clearly bugged and anyone who attempts to install it should ensure they have a good copy of their SQL database like I do.