Unknown table
promes - March 13, 2008 - 21:03
| Project: | Google Proxy Hacking Protector |
| Version: | 5.x-1.2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Somehow this module doesn't confirm to the drupal-standards. It needs some tables, but searches for the wrong one's. Why? In my installation each table gets a prefix as standard can be set in the Drupal sites/default/settings.php file. All installed modules work with correct table-names (including the prefix) but not this one?
The module creates the 2 tables correctly. Also I found data in the tables based on my preset preferences. But when these data are used the tables are not found.
So it defaults to be useless for me.
Has anyone a clue what's wrong?
#1
Well, I received an 'unknown_table' error message, too. After checking the tables in my database I found, that the 'antiproxyhack_cloak_update' table lacks an index. In phpMyAdmin you can add indices simply by clicking on an icon. You have to do that twice as the table has 2 fields.
After accomplishment the error disappeared in my case.
#2
Update:
In the module php-script find the following lines:
// retrieve cloaking data filtered by the supplied parameters
function antiproxyhack_get($id = 0, $spider_name = '', $record_type = '', $value = '', $wildcard_value = '', $is_user_defined_data = '', $not_spider_name = '') {
// by default, retrieve all records
$q = " SELECT antiproxyhack_cloak_data.* FROM {antiproxyhack_cloak_data} WHERE TRUE ";
After the SELECT command manually add your table prefix right before antiproxyhack_cloak_data. Don't do this to the argument after FROM !!!
Save, upload and thereby replace the old version of that module script and go ahead. Should work.