Error when creating new user with unassigned role

Okay. First thing to do is to check and see if the two database tables were even created. If they weren't, let me know - that might signify a problem with your database user's permissions.

Next, if the tables are created, check the contents of them. One of them should have some fake roles defined - "All users" and "Group owners" or something like that. Tell me if one or both are missing.

Those are the only causes for that first error message. There are 4 queries executed at install, create table 1, create table 2, insert role 1, insert role 2. That's it. Let me know.

What version of MySQL are you using? 4.x I'm guessing. I don't think 4.x likes these lines: /*!40100 DEFAULT CHARACTER SET utf8 */ in the install file. Try uninstalling the module (you'll get errors, but ignore them), and then reinstalling after you delete the code like that one. Don't delete the parenthesis just before that code. You need it in both places.

In other words, change this: ) /*!40100 DEFAULT CHARACTER SET utf8 */ to this: ) in both places for your database.

You can try to execute the SQL queries that go along with $query3, and $query4 manually from within phpmyadmin or similar.

INSERT INTO og_multi_mand_groups_role VALUES (-1, 'All users', '');
INSERT INTO og_multi_mand_groups_role VALUES (0, 'Group admins', '');

If you have a prefix on your tables, adjust table names as needed.

Refresh my memory, did you, or did you not have the regular og_mandatory_group module previously installed? Do you still have these variables: og_mandatory_group_admin & og_mandatory_group in your variables table? If you do, perhaps that is where the problem lies. It won't matter if that module is installed or not because it leaves behind these variables (i.e. doesn't clean up after itself).

That gives me more to look at, so that's progress. The devel module would be useful here to find out where the form.inc errors originate from. Use the 'backtrace' feature. This my my first module. Since then, I've learned a lot more. Perhaps it's as simple as checking to see if an array is empty before trying to execute certain parts of code. So try the devel module and let me know.

It might not be easy to re-produce the same behavior again

I don't want you to waste your time. Perhaps if someone else has a similar issue, simply reading this post will help them and they can try to give the devel info. However, that would mean I'll have to wait until someone else has a problem before I can think about fixing it. Not ideal, but if you've got deadlines, etc., I don't want to keep you from them.

I'm getting a similar issue. When I try and edit one of the pages I've got, I get the following:

warning: Invalid argument supplied for foreach() in [paths hidden by me]/includes/form.inc on line 948.

I also get an error when I view the page. It is:

* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'NOT IN ('25') OR .tid IS NULL))' at line 1 query: SELECT count( DISTINCT(node.nid)) FROM node node WHERE (node.type IN ('prayerpost')) AND ((.tid NOT IN ('25') OR .tid IS NULL)) in [paths hidden by me]/includes/database.mysql.inc on line 172.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'NOT IN ('25') OR .tid IS NULL)) ORDER BY node_created_created DESC LIMIT 0, 20' at line 1 query: SELECT DISTINCT(node.nid), node.created AS node_created_created FROM node node WHERE (node.type IN ('prayerpost')) AND ((.tid NOT IN ('25') OR .tid IS NULL)) ORDER BY node_created_created DESC LIMIT 0, 20 in [paths hidden by me]/includes/database.mysql.inc on line 172.

We're on MySQL 5.0.48 and PHP 5.1.6. We're seeing this error after migrating to a new host (we're dedicated though, so I can change anything I need to).

Unfortunately, I don't see anything in your message that would indicate a definite problem originating in this module. It you indeed have a problem with OG, and not this module, it is better that you open a new issue as you can clearly see that the maintainer of OG doesn't appreciate tack-on problems to other issues being moved to his queue.

Found this bug during a debugging of a site.

Turns out that if you have roles assigned when creating a new user, even if All Users is set correctly, the extra role (which MMG doesn't know about) throws an error like so:

warning: Invalid argument supplied for foreach()
in [...]/sites/all/modules/og_multiple_mandatory_groups_by_role/
og_multiple_mandatory_groups_by_role.module on line 924.

I suspect it's hitting the assigned group and not dealing with the empty result set here:

$mandatory_groups = unserialize($result->mand_groups);
foreach ($mandatory_groups as $key_g => $value_g) {

Short term fix:

make sure all roles have been entered into MMG, even if they have no groups attached to them. No error then.

The error you are getting occurs well in advance of the code you quoted which happens when the user is inserted. Line 924 has to do with the registration form.

Question: Do you have (want) a group to be mandatory for all users? If not, you should not have to set it.

Likewise, you should not have to include all roles in the admin for this module. I certainly never have.

Regarding line 924, the only foreach in the vicinity (which makes me wonder if you're using the latest version), uses the array of mandatory groups from the database. So an error there tells me that the database doesn't have the correct values stored, which tells me that perhaps something is wrong with your admin settings for MMG. Perhaps you could include some screen shots of your settings?

You could also try to print the contents of the mandatory group array just before the line that gives you the error so that we know why it doesn't like the argument. You can use the devel module on 'backtrace' mode, then save the 'complete' page and zip/attach it to your next post. What that does is tell us each function call and all arguments leading up to the crash.

Indeed, wasn't the latest version of code. (I've since updated it...) "Never mind" - Emily Litella