Mollom is not compatible with user profiles as nodes

On the first pass through the registration form, things actually behave as intended since the $GLOBALS['mollom_response'] has yet to be set. If you fail validation on the form, however, subsequent loads of the page have $GLOBALS['mollom_response'] set from the mollom-enabled form, and therefore all subsequent forms cascade into the if statement. The incorrect form (i.e. the node form in this case) is still barging into the session-id section since the $GLOBALS value is set by the user_register form. The easiest and most straightforward solution is to require the session section to be run on only mollom-enabled forms (rather than all forms on a mollom-enabled page as is happening currently). This will not allow you to trigger both the node form and the user registration to have mollom checking, but will probably solve the issue for most individuals.

This patch also worked for me on a 5.x site with a Node Profile form on the user registration page.

I applied this patch to Mollom 5.x-1.6, disabled Mollom filtering on the user registration form and the user profile form, and the user profiles still did not load. When I grant users the "Post with no checking" permission, they are able to view the user profiles.

Actually, never mind. My problem was completely unrelated to Mollom. It actually had to do with some code that we had put in the Contemplate module for user profile which was calling the Guestbook module and causing a cascade of errors. Mollom filtering is working fine on all our nodes.

If the patch in #1 fixed the issue, then this should be already be fixed in the latest release due to other changes.