Status codes not saving and User Warning errors
| Project: | Signup Status |
| Version: | 6.x-1.0-alpha2 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I'm having some problems getting Signup Status running. I just downloaded Signup_Status 6.x, and enabled it, running alongside Signup 6.x-1.0-rc5. When I tried to add new signup status codes, it gave me a message saying that the new status code I entered has been created, but nothing appears on the list. I confirmed in the Signup settings that although the other signup_status settings are present, there are no status codes for me to add limits to.
I then realized there was a newer rc6 release of Signup, so I downloaded and installed that (and ran update.php). But now on every page on the site I see this error:
* user warning: Unknown column 'weight' in 'order clause' query: SELECT * FROM signup_status_codes ORDER BY weight in /export/www-ets-dev/htdocs/sites/all/modules/signup_status/signup_status.module on line 382.
* user warning: Unknown column 'weight' in 'field list' query: INSERT INTO signup_status_codes (name, description, mod_signup_count, show_on_form, weight) VALUES ('Enrolled', '', 1, 0, 0) in /export/www-ets-dev/htdocs/includes/common.inc on line 3436.
* user warning: Unknown column 'weight' in 'order clause' query: SELECT * FROM signup_status_codes ORDER BY weight in /export/www-ets-dev/htdocs/sites/all/modules/signup_status/signup_status.module on line 382.
Any ideas what I'm missing?
Thanks!
#1
Sounds like your DB schema is out of date with the latest code. Are you really running signup_status 6.x-1.0-alpha2? Did you install it from scratch or update from a previous release? If you upgraded, did you run update.php? What does the following SQL query against your DB say?
SELECT name, weight, schema_version FROM system WHERE name RLIKE 'signup';(assuming your site doesn't use a DB table prefix -- if so, prepend that to "system" in the query...)
As I wrote in the release notes, to use signup_status alpha2 you have to run signup 6.x-1.0-rc6 or later...
And, the alpha2 release definitely includes some schema changes, which it seems your site doesn't yet have.
#2
I can confirm this (at least for the way I updated the module...). I used drush to update from alpha1 to alpha2, which reported there were no DB updates to perform.
I subsequently used drush to update signup from rc5 to rc6 and the DB update automatically ran without a hitch.
I then checked out the signup_status admin page and got the listed error (and none of the status codes I'd previously created). I then visited update.php and the update wasn't automatically selected to run, so I manually selected it and ran it successfully. Then the admin page gave no error (and listed the status codes I'd previously put in).
(So now I'm wondering if something's broken somewhere because the DB updates occurred in the wrong order as specified in the release notes, gah :P)
Don't know if the bug somehow lies in this release or with drush or with update.php...
mziegmann: did you use drush to update to alpha2?
#3
Sounds like a critical bug in drush then. :( alpha2 introduced signup_status_update_6000() to signup_status.install. That's means you need to run the update. If drush says there are no DB updates to perform between alpha1 and alpha2, it's full of shiz...
#4
Sorry for the delayed response. Confirmed I am using Signup Status 6.x-1.0-alpha2 and Signup 6.x-1.0-rc6. Signup Status was a fresh install, but Signup rc6 was an update. I don't use Drush, but did recheck udpate.php to be sure there were no outstanding updates.
In follow-up, I disabled and deleted the module altogether and started over - and the problem has gone away. I'm assuming then the problem had to do with the fact that I updated to Signup rc6 AFTER installing Signup Status alpha2? Either way, problem resolved. Thanks!
#5