Warning "Table doesn't exist" is shown after upgrading to nodewords 6.x-1.3-beta5
Aminto - November 6, 2009 - 10:09
| Project: | Nodewords |
| Version: | 6.x-1.3-beta5 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hi,
I've upgraded from an earlier version to the latest Nodewords version and get the following message:
user warning: Table 'myname_drpl4.nodewords_custom' doesn't exist query: SELECT * FROM nodewords_custom ORDER BY weight ASC in /home/myname/public_html/sitename.com/sites/all/modules/nodewords/nodewords.module on line 1257.
This appears on every page of the site after the upgrade and therefore I've had to disable it for now. I've tried configuring it and so on, but this doesn't resolve the problem. Any help would be greatly appreciated!
#1
From which version did you update?
Did you run update.php after copying the new files?
The table is created from the installation function, and from the following update function:
<?php
/**
* Implementation of hook_update_N().
*/
function nodewords_update_6115() {
$ret = array();
if (db_column_exists('nodewords', 'weight')) {
db_drop_field($ret, 'nodewords', 'weight');
}
if (db_table_exists('nodewords_page_weight')) {
if (!db_table_exists('nodewords_custom')) {
db_rename_table($ret, 'nodewords_page_weight', 'nodewords_custom');
}
else {
db_drop_table($ret, 'nodewords_page_weight');
}
}
elseif (!db_table_exists('nodewords_custom')) {
db_create_table($ret, 'nodewords_custom',
array(
'fields' => array(
'pid' => array(
'type' => 'serial',
'not null' => TRUE,
),
'path' => array(
'type' => 'varchar',
'length' => 255,
'not null' => TRUE,
'default' => '',
),
'weight' => array(
'type' => 'int',
'size' => 'tiny',
'not null' => TRUE,
'default' => 0,
),
'enabled' => array(
'type' => 'int',
'size' => 'tiny',
'not null' => TRUE,
'default' => 1,
),
),
'primary key' => array('pid'),
'unique keys' => array(
'path' => array('path'),
),
)
);
}
return $ret;
}
?>
#2
#3
#4
Automatically closed -- issue fixed for 2 weeks with no activity.