* warning: array_keys() [function.array-keys]: The first argument should be an array in /srv/www/htdocs/sites/all/modules/salesforcewebform/salesforcewebform.module on line 204.
    * warning: Invalid argument supplied for foreach() in /srv/www/htdocs/sites/all/modules/salesforcewebform/salesforcewebform.module on line 204.

This error seems to be coming up whenever I try and save my custom fields on the Site Config page. Error 204 is within the "create_custom_field_spec" function, so it sounds like it's tied to the custom fields. Let me know if you need any more info! Thanks for porting this so quickly!

Comments

obsidiandesign’s picture

obsidiandesign commented
Status: Active » Fixed

Small FormAPI change that I didn't properly implement. The custom validation function wasn't working properly, causing the error. Fixed in the CVS and will show up in the next -dev release (midnight or so).

Bryan

Status: Fixed » Closed (fixed)

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

amariotti’s picture

amariotti commented
Priority: Normal » Critical
Status: Closed (fixed) » Active

I'm still getting this error in the -dev release.

Also, while looking around today I saw an error corresponding to my Webforms that are using the Salesforce Webform plugin. I went and tested it out and it's sending me to a white screen of death! It needs to be looked at ASAP. (Note: we just upgraded our site yesterday to Drupal 6.x)

Thanks,
Andrew

amariotti’s picture

amariotti commented

Also, when I go to the Site Config page I don't see anything in the custom fields field but when I look in the database the custom field stuff is all there. Not sure what needs to be done here but it appears that I've got some issues. :)

obsidiandesign’s picture

obsidiandesign commented
Version: 6.x-1.0 » 6.x-1.1
Status: Active » Fixed

Seems the change I originally intended to fix this issue didn't. Corrected in 6.x-1.1.

Bryan O'Shea
Obsidian Design

amariotti’s picture

amariotti commented

Great! Thanks!

Status: Fixed » Closed (fixed)

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