When going to the My Account page and trying to edit registration information created with the registration modification module and all the other required modules for this, I get the following error and no edit form is displayed. I think it might have to do something with the subform element module. Since it is the $type subform that gives the error.

warning: Illegal offset type in /var/www/vhosts/codefellas.com/subdomains/bannerich/httpdocs/includes/form.inc on line 894.
warning: Illegal offset type in /var/www/vhosts/codefellas.com/subdomains/bannerich/httpdocs/includes/theme.inc on line 167.
warning: Illegal offset type in /var/www/vhosts/codefellas.com/subdomains/bannerich/httpdocs/includes/theme.inc on line 168.
warning: Illegal offset type in /var/www/vhosts/codefellas.com/subdomains/bannerich/httpdocs/includes/theme.inc on line 170.

I'm using all the latest versions of all the modules.

CommentFileSizeAuthor
error.gif30.46 KBfuse

Comments

dnaromance’s picture

dnaromance commented

Hi,

I've faced it too! Any solution for this?

I'm using nodefamily, subform, nodeprofile, pageroute, accounttypes, and membership types and registration modification. I initial suspect there must be something to do with among these.

When I click on "Personal Data" then it's ok, but when I click on "Profile" then it shows an errors above. I think something to do with my content type "Profile", others might also cause the error were account types and pageroute. I suspect that.

I appreciate any response regarding this issue. Hope could resolve this issue. Thanks :)

Best regards,
kailoon

toemaz’s picture

toemaz commented
Status: Active » Fixed

In hook_user, when a module returns a form, I noticed that the error gets away when you use a nested form array:

        $form['blah'] = array(
          '#type' => 'fieldset',
          '#title' => 'blah',
        }
// should become
        $form['toto']['blah'] = array(
          '#type' => 'fieldset',
          '#title' => 'blah',
        }

Status: Fixed » Closed (fixed)

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