Schema error upon list activation

I can't reproduce it. It seems that the module installion did not run properly.
Could you unistall user mailman register and reinstall it?
What the log errors?
What your database backend?

I uninstalled user mailman register, then reinstalled. Same issue.
I uninstalled user mailman register and additionally mailman manager, and then reinstalled, ran update, and then reinstalled user mailman manager.
The columns are simply not getting added to the mailman_lists table, although during install of user mailman manager, I get no errors. Not even in the log.
The only log errors are related to trying to activate a lists when columns are missing.
I'm using mysqli and mysql5.

I've developed the module on a mysql5 backend and i don't have this bug.
Just only to be sure, did you uninstalled the modules tables after unchecked them? I mean from the http://yoursite/drupal/?q=admin/build/modules/uninstall page?
Any info is logged in your sql and/or apache log files (/var/log) ?

I would post this as critical since this blocks the functionality of this module. I'm getting this similar error when adding a new list entry.

user warning: Unknown column 'allow_unsubscribe' in 'field list' query: UPDATE mailman_lists SET webpass = '......', webadmin = '.....', user_invite = '0', user_notify = '1', user_admin_notify = '1', allow_unsubscribe = '1', allow_temp_disable = '1', allow_digest = '1', description = '' WHERE lid = 3 in /....../public_html/sites/all/modules/user_mailman_register/user_mailman_register.module on line 588.

I've noticed that user_mailman_register.module doesn't install any database tables, whereas mailman_manager does and that module doesn't even include the columns that user_mailman_register needs.

(Please email me if I can help test out any patches.)

user_mailman_register does not install any table, but it alters mailman manager table by adding some columns (for example the "allow_unsubscribe" column). The code in in user_mailman_register.install .
In your case, it seems that the module installation process did not worked correctly. Please, could you try to unistall user_mailman_register (it's important to do this also in the admin/build/modules/uninstall page) and reinstall it and check for installation errors.
If no errors and still not work, what are your database backend and your drupal and db versions?

Considering closed because no more info added

Same error: drupal 5,mysql5,

I see that this was closed -- basically, the maintainer does not acknowledge the errors?
Disappointing.

user warning: Unknown column 'version' in 'field list' query: UPDATE mailman_lists SET webpass = 'xoxoxo', webadmin = 'http://example.com/mailman/admin/example', version = '0', user_invite = '1', user_notify = '1', user_admin_notify = '1', allow_unsubscribe = '1', allow_temp_disable = '1', allow_digest = '1', description = 'xoxoxox' WHERE lid = 1 in /home/ooo/domains/ooo.org/public_html/includes/database.mysql.inc on line 172.

iteachnet.org,
I'm sorry that you think i did not acknowledge the errors.
I did, but i can't reproduce it when following the standard module installation and upgrading procedure and had no feedback in my request.
However, the error you reported seems very different from the opening one, i'm quite sure that you simply did not follow the module upgrade procedure: http://drupal.org/node/250790.
Could you check it?

Same problem. trying to make anonymous subscription possible.

The system: Dreamhost. Drupal 6.12. Installing only non-beta modules as much as possible.

Installed mailhandler and listhandler first, working fine, reading a imap mailserver.

Then I installed mailman manager. Added a request emailadres.

Then I installed this module. I notices in the modules page that it gave me an error, lots of red lined about MySQL permission problems in the database. Refreshed, and they were gone, so I hoped everything had worked anyway.

but then when I try saving settings I too get this error (user warning: Unknown column 'webpass' in 'field list' query: etc)

And that's how I got here :-)

Ok, some more data:

I was trying to uninstall the module, and I got loads of these:

* user warning: ALTER command denied to user '...'@'localhost' for table 'mailman_lists' query: ALTER TABLE mailman_lists DROP webadmin in /..../includes/database.mysql-common.inc on line 322.

and I remembered that the error I saw in the modules page, after installing, were also about ALTER.

I thought I'd try the beta.

uninstalled through drupal, then removed the folder through FTP.

Uploaded the beta. Refreshed module list, and saw the two options. Checked the first one, clicked 'save' and...

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 74333 bytes) in /...includes/database.mysqli.inc on line 303

As reported in #12, your provider (or system administrator) is denying the ALTER sql command.
This command is required by drupal itself as you can read in http://drupal.org/requirements#database.
Ask your system administrator to enable it or you'll probably not be able to correctly use most of drupal modules (included UMR) and, in the future, the Drupal core itself because it' s often needed for the upgrading procedure.
The memory error probably is a consequence of the missed upgrading UMR procedure.

I'm also having this problem. mysql 5.0.22

Exactly what problem? #1 error?
Did you follow the upgrade procedure described at http://drupal.org/node/250790?
Does your provider supports the drupal requirements describe at http://drupal.org/requirements?
Is any error logged?

Thanks for checking; I appreciate your effort. Honestly.
The thing I don't understand about your comment is that I did not upgrade. It was a new installation.

Ok, now it's clear.
I forgot to add the "version" field in the 5.x module main installation.
Fixed with http://drupal.org/cvs?commit=245876.
However, since this field is correctly added by the upgrading procedure you can fix it without reinstalling the module simply running the drupal upgrade procedure and selecting the n. 3 user_mailman_register update.
This bug is not related to the opening issue and the #5 and #12 comments. I'm still sure that they belongs to a missed upgrading procedure or to the minimum requirements not met as explained in #14.

Considered as fixed. Feel free to reopen this issue if the problem persists, but please open a new one if the error message is different from those reported here.

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