I get the following errors when updating the database after the Beta4 upgrade:

* user warning: Table 'databasemysite.autoassignrole_page' doesn't exist query: ALTER TABLE autoassignrole_page ADD menu VARCHAR(255) in /usr/local/apache2/vhosts/mysite.com/htdocs/sites/all/modules/autoassignrole/autoassignrole.install on line 156.

* user warning: Table 'databasemysite.autoassignrole_page' doesn't exist query: SELECT rid, path, display, title, weight, menu FROM autoassignrole_page in /usr/local/apache2/vhosts/mysite.com/htdocs/sites/all/modules/autoassignrole/autoassignrole.module on line 31.

Comments

13rac1’s picture

13rac1 commented

Can you verify if the table autoassignrole_page exist or not in your database? Do you have a database table prefix set?

cyberswat’s picture

cyberswat commented

Actually there isn't an update hook to move from beta to beta so the best approach is to completely uninstall the module and recreate it so that the database tables are created during the install.

gregarios’s picture

gregarios commented

Ok... well that explains why the new version seems to be working as well. Why should there be an error in the database update then?

cyberswat’s picture

cyberswat commented

The only error you are likely to see would be something focusing on the statement "ALTER TABLE autoassignrole_page ADD menu VARCHAR(255)" ... you'll get an error if that field already exists. The update hook that does that was put in place in case you were already running a version that created the autoassignrole_page table. So if you did a clean install that statement will fail because the field already exists. Is this what you are seeing?

gregarios’s picture

gregarios commented

I had been using Beta3.

I put the site in maintenance mode.

I then deleted the "autoassignrole" folder from the modules directory, and replaced it with the new Beta4 version of the "autoassignrole" folder.

Then, I went straight to the database update and ran it, getting the errors I listed.

I suppose if I'd tried to run the new module (not in maintenance mode) before updating the database (wrong procedure) then the table entry would have been installed there and I may not have gotten the error?

cyberswat’s picture

cyberswat commented

You need to uninstall by navigating to the modules page. Disable the module. Click the uninstall tab. Select the auto assign role module and submit. Then enable the new code.

cyberswat’s picture

cyberswat commented
Status: Active » Fixed

Added update hooks to resolve this issue
http://drupal.org/cvs?commit=252054

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.