Undefined table weight_weights after upgrading from 7.x-2.0-beta3

Hi!
As asked here, the schema_version in system tabel is 7204

Yes, many nodes.. 12000 :(
The weight is active only in one content type

I'm having this issue also and I have 2 nodes on the entire site.

Is RC1 the fixed release or dev?

I still had issues with this error when upgrading to RC1.

This is what I get. Just tried the update from beta3 to r1 on a different site and got the same thing:

Error message
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table '515871_trfsd7.weight_weights' doesn't exist: SELECT weight FROM {weight_weights} WHERE entity_id=:id AND entity_type=:type; Array ( [:id] => 2 [:type] => node ) in _weight_get_weight() (line 381 of /sites/all/modules/weight/weight.module).
The website encountered an unexpected error. Please try again later.

That's the error that shows up when I got to update.php. But the rest of the site is broken with this error:

Error
The website encountered an unexpected error. Please try again later.

The schema_version is 7204.

I just tried the latest dev and still receive the same error.

This is what the apache error log says:

[Mon Apr 02 09:45:09 2012] [warn] mod_fcgid: stderr: PHP Fatal error: Call to undefined function _weight_get_types() in /home/d7/public_html/sites/all/modules/weight/weight.install on line 199

So, this change will be in the next dev release?

I just tried to update from beta3 to rc2 and got the same error from comment #10

I still see the error from #10 in rc2. - when upgrading from 7.x-1.0

When updating from beta3 to the current dev release (as of 5 minutes ago) I still get this error on every page of the site and in the error logs:

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'dbtest.weight_weights' doesn't exist: SELECT weight FROM {weight_weights} WHERE entity_id=:id AND entity_type=:type; Array ( [:id] => 2 [:type] => node ) in _weight_get_weight() (line 442 of /home/test/public_html/sites/all/modules/weight/weight.module).

I can still test this for you if you want, but I've moved my sites to using the Draggable Views module, so if you can't reproduce it and I'm the only one experiencing this error then you are welcome to close the issue.

Completely uninstalling beta3 and reinstalling the rc2 also works fine. It's just the upgrade path that is broken.

@10oclock : yes this is still reproducible with the current 7.x-2.x-dev

Seems that I've finally tracked that one down. Here is the a backtrace showing the exception (which happens during bootstrap):

WD php: PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'style.weight_weights' doesn't exist: SELECT weight FROM    [error]
{weight_weights} WHERE entity_id=:id AND entity_type=:type; Array
(
    [:id] => 2
    [:type] => node
)
 in _weight_get_weight() (line 443 of /var/www/drupal7/drupal/sites/all/modules/weight/weight.module).
#0  _weight_get_weight(stdClass Object (…)) called at [/var/www/drupal7/drupal/sites/all/modules/weight/weight.module:334]
#1  weight_node_load(…)
#2  call_user_func_array(weight_node_load, Array (…)) called at [/var/www/drupal7/drupal/includes/entity.inc:334]
#3  DrupalDefaultEntityController->attachLoad( … ) called at [/var/www/drupal7/drupal/modules/node/node.module:3945]
#4  NodeController->attachLoad( … ) called at [/var/www/drupal7/drupal/includes/entity.inc:204]
#5  DrupalDefaultEntityController->load(Array ([0] => 2), Array ()) called at [/var/www/drupal7/drupal/includes/common.inc:7623]
#6  entity_load(node, Array ([0] => 2)) called at [/var/www/drupal7/drupal/sites/all/modules/redirect/redirect.module:1045]
#7  redirect_load_entity_from_path(node/2) called at [/var/www/drupal7/drupal/sites/all/modules/redirect/redirect.module:217]
#8  redirect_url_inbound_alter(node/2, node/2, ) called at [/var/www/drupal7/drupal/includes/path.inc:272]
#9  drupal_get_normal_path(node/2) called at [/var/www/drupal7/drupal/includes/path.inc:21]
#10 drupal_path_initialize() called at [/var/www/drupal7/drupal/includes/common.inc:5031]
#11 _drupal_bootstrap_full() called at [/var/www/drupal7/drupal/includes/bootstrap.inc:2186]
#12 drupal_bootstrap(7) called at [/usr/share/drush/includes/environment.inc:977]
#13 _drush_bootstrap_drupal_full() called at [/usr/share/drush/includes/environment.inc:194]
#14 drush_bootstrap(5, 6) called at [/usr/share/drush/includes/environment.inc:310]
#15 drush_bootstrap_to_phase(6) called at [/usr/share/drush/drush.php:90]
#16 drush_main() called at [/usr/share/drush/drush.php:41]

As you can see the main point is entity_load being called by redirect's redirect_url_inbound_alter implementation which in turn calls hook_node_load.
Bootstrapping is done even on update.php or drush updb.

A simple workaround for this is to disable either weight and/or redirect during bootstrap. Disabling redirect worked for me.

Another problem seems that 7202 does something infeasible for my installation. (It breaks after 10mins because it hits the 1GByte memory_limit). But I'll open a separate report for that.

Ok there seems to be an error in the batch-handling that was implemented earlier in this bug-report. Here's a fix.

I just tried to upgrade version 1.0 to release version 2.0 from May 19th and got the following error.. Hopefully its useful..

Additional uncaught exception thrown while handling exception.
Original

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'jsm2djc_website.weight_weights' doesn't exist: SELECT weight FROM {weight_weights} WHERE entity_id=:id AND entity_type=:type; Array ( [:id] => 4 [:type] => node ) in _weight_get_weight() (line 442 of /home/jsm2djc/public_html/sites/all/modules/weight/weight.module).
Additional

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'jsm2djc_website.weight_weights' doesn't exist: SELECT weight FROM {weight_weights} WHERE entity_id=:id AND entity_type=:type; Array ( [:id] => 4 [:type] => node ) in _weight_get_weight() (line 442 of /home/jsm2djc/public_html/sites/all/modules/weight/weight.module).

Yes, this site does have redirect enabled and its needed for this particular site so disabling it isn't really an option..

Will Weight 2.0 and redirect simply not work together?

Note that it's enough to disable either weight or redirect. As long as non of them is uninstalled update hooks are run for both!

Perhaps you should put a notice about that somewhere prominent on the module page and the upgrade instructions in the README.txt. Redirect is a very common module (we use it for nearly all of our sites) so this is going to hit a lot of people.

For upgrading from 1.0 you actually could do something:
1. Release a new stable 1.1 version that already creates (but doesn't use) the table.
2. change the upgrade hooks so that they don't fail if the table was already created.

For the future: Maybe you shouldn't mark a stable 1.0 release as unsupported as long as there is no stable 2.0 release. This was forcing people to upgrade to 2.0 pre-releases too early.

I had to upgrade several sites which currently run 7.x-1.0 to 7.x-2.1 without interruptions. For that I've written two patches:

• The first applies to 7.x-1.0 and creates the weight_weights table when drush updb is called.
• The second applies to 7.x-2.1 and makes weight_update_7200() work when weight_weights is already created

So the upgrade-path is:

1. patch the current 7.x-1.0 with the first patch
2. drush updb
3. upgrade the code to 7.x-2.1+patch
4. drush updb

You can forget about those patches as soon as the sites are upgraded to 2.1.

Added additional reference.