warning when editing content type

same here, same versions. happened after upgrading Multilanguage to 6.x-1.0-beta3 (from beta2)

Same issue. Some further info:
Running d6.4, i18n v 1.0-b3 on a fresh install/fresh db.

I notice this when editing some of the content types though. There is no difference between my content types, yet the error shows up for "page", but not for "press_releases".

add this line on line 74

 if ( ! isset($data['#options'])) { return; }

Thanks, it worked for me.

awesome, works for me too

Brilliant! Thanks too.

Thanks, alan.oliveira. I made a small improvement and created a simple patch file. If this works for you, please respond and flag this patch as having been reviewed and tested by the community.

well... how do I use this patch anyway?
juts copy and paste on line 74 ?

the handbook has information on how to apply a patch: http://drupal.org/node/60108

or you could do it by hand as you suggested. the lines which start with a + symbol are to be added between the existing lines (if there were any starting with a - symbol they would have to be removed). just find the corresponding section of the function i18nsync_form_alter() and add the three lines i wrote. but as the handbook says be sure to back up your files and your database first just in case!

once you've tried that, please come back and report your experiences. if there's a problem, i'll try to fix it. if everything works great, leave a positive review to help the module maintainers know that this patch should be considered for the next version.

Code snippet tested, it took care of the warning on the poll module.

Will this be included in the next version of the module or will we need edit this file each time? I have not needed to patch a module before.

Thanks,
Steve

@denverdataman: the maintainer(s) of this module will mark the status of this issue as "fixed" when this issue has been resolved, by including this patch, or by some other means. until then you'll need to apply this small patch. as always with drupal, if you want to help the maintainers evaluate whether this patch actually solves this problem, you could test it and leave a brief review here. the more people who test a patch, the sooner it's likely to be included in the next version.

Thanks