Updrading from modr8 6.x.1.3 to modr8 7.x.dev gives error site wide

Yet to look into the upgrade.

this lock the website with 100% success. But hopefully we can still disable the module later (drupal bootstrap isn't locked).

I had no modr8_moderate table in my D6 DB, so :
1) This table should not be renamed if it does not exists
2) This table should be created (modr8_schema ?) if it can't be upgrade.
In D6 I only had modr8_log and AFAIR it worked.

Previously we had a plan to have separate table to store modr8 information. However now we decided to add the modr8 field like in D6.

This needs few hours of my work and extensive testing that I can't put it now. Hopefully before new year I will try to give a alpha release.

I'm getting this same error:

Update #7001
Failed: DatabaseSchemaObjectDoesNotExistException: Cannot rename <em class="placeholder">modr8_moderate</em> to <em class="placeholder">modr8</em>: table <em class="placeholder">modr8_moderate</em> doesn't exist. in DatabaseSchema_mysql->renameTable() (line 304 of /home/******/public_html/*****.com/includes/database/mysql/schema.inc).

Here is a sample from the logs, which happens even after I disable the half-upgraded module:

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'base.moderate' in 'field list': SELECT revision.vid AS vid, base.uid AS uid, revision.title AS title, revision.log AS log, revision.status AS status, revision.comment AS comment, revision.promote AS promote, revision.sticky AS sticky, base.nid AS nid, base.type AS type, base.language AS language, base.created AS created, base.changed AS changed, base.tnid AS tnid, base.translate AS translate, base.moderate AS moderate, revision.timestamp AS revision_timestamp, revision.uid AS revision_uid FROM {node} base INNER JOIN {node_revision} revision ON revision.vid = base.vid WHERE (base.nid IN (:db_condition_placeholder_0)) ; Array ( [:db_condition_placeholder_0] => 3374 ) in DrupalDefaultEntityController->load() (line 196 of /home/*****/public_html/*****.com/includes/entity.inc).

I'm about 12 hours into a difficult upgrade from D6 to D7 and I can't seem to remove the module completely either. Is there a step-by-step way that we could fix it or remove the entire module manually? Something like:

1. create (or delete) a new table called ___ in your database
2. [do something else?]

I don't need the Modr8 module on the site at the moment, but I'm trying to either find a way to remove it or fix it so I can finish the upgrade...

disable and uninstall it from your D6 DB before the upgrade.

OK but what if I can't do that, because I upgraded many modules and don't want to do it again ? Any alternative solution ?

Attached is a patch against the latest 7.x-dev branch that fixes the source of the error. This came from the fact that the update script was trying to rename "modr8_moderate" instead of "modr8_log" which was the actual table name used in D6.

Nevermind about this patch. While it fixes the table name, it doesn't correctly migrate the moderated nodes into the {node} table. I haven't had a chance to evaluate whether or not this module even works... maybe one day after I'm done with this upgrade.

I ran into the same error described by the OP (vusani) when upgrading my Drupal 6 site to Drupal 7. The modr8 version was 6.x-1.3 before upgrade. At the time of this comment the Drupal 7 modr8 version is 7.x-1.x-dev.

I ended up creating a patch for myself to fix this issue with help from hargobind's patch (#7). Hopefully it can help the next person that comes across this issue.