I'm running Drupal 6.10. I enabled the addresses module and added an address field to my content type, and now I'm getting these errors:

    * warning: Illegal offset type in siteroot\includes\form.inc on line 1363.
    * warning: Illegal offset type in siteroot\includes\form.inc on line 1363.
    * warning: Illegal offset type in siteroot\includes\form.inc on line 1363.
    * warning: preg_match() expects parameter 2 to be string, array given in siteroot\includes\bootstrap.inc on line 771.
    * warning: preg_match() expects parameter 2 to be string, array given in siteroot\includes\bootstrap.inc on line 771.
    * warning: preg_match() expects parameter 2 to be string, array given in siteroot\includes\bootstrap.inc on line 771.

Disabling the module resolves the issue.

Comments

andersonmh’s picture

andersonmh commented

+1 - Subscribing
Has there been a patch on this?

kriskd’s picture

kriskd commented

Just got this error as well.

selwynpolit’s picture

selwynpolit commented

Me too. It would be nice to use this.

Iowagirl’s picture

Iowagirl commented

I was able to remove the error by choosing "none" instead of "hidden" under the User addresses fields option.

pimok3000’s picture

pimok3000 commented
Title: Errors on my content creation page » Errors on my content creation page, but error coming from coresearches module

I Get the same error, but without having the Adresses Module installed. With my installation it seems to be an issue with the coresearches module. When i disable these 2 modules

Content search 6.x-1.0 (or last dev, doesn´t make a difference)
User search 6.x-1.0 (or last dev, doesn´t make a difference)

all is well again.

Maybe it has something to do with the patch that normally needs to be applied besides installing the module, but i didn´t apply it as it changes to much core code. By simply disabling the coresearches Module solves the problem.

imp7’s picture

imp7 commented

I confirm this error, when I changed it to none and saved there is no error. However when I edit the field again after saving all the values are lost and set to normal instead the field configure form. This must be only in the form as the values are still set to none in the add node form.

codycraven’s picture

codycraven commented
Status: Active » Postponed (maintainer needs more info)

Can someone who is having this issue please try to reproduce the error with the current dev release?

If you are able to reproduce the error please include all steps taken and other contributed modules that are installed.

I have not been able to come across this issue.

ampdude’s picture

ampdude commented

Hi there. I hope I'm posting in the right place, as I'm a n00b here and all. I had the same Illegal offset error as well. I am using 6.x-1.06. I do not have the core search enabled. The error definitely appears when setting fields to 'hidden' and disappears when set to 'none.' I haven't seen settings revert, though. So far, what has been set to 'none,' continues to remain at, 'none.'

codycraven’s picture

codycraven commented
Status: Postponed (maintainer needs more info) » Needs work

ampdude, thanks for the update. I see the error when setting an option to hidden - this is something that I will look to resolve before the next release.

If anyone else has time to research a solution for this please post a patch :D

codycraven’s picture

codycraven commented
Title: Errors on my content creation page, but error coming from coresearches module » Error when setting fields to hidden
Version: 6.x-1.05 » 6.x-1.06
codycraven’s picture

codycraven commented
Status: Needs work » Closed (duplicate)

#512354: Error upon setting fields to "none"

libak’s picture

libak commented

Try set the #type to 'value' instead. I had a Select List which I wanted to be hidden and I got the error Removed by changing the type.

AlexisWilke’s picture

AlexisWilke commented
Status: Closed (duplicate) » Active

I'm reopening this one because I do not think this is a duplicate of #512354: Error upon setting fields to "none".

And today I was finally able to see the CCK working. I made many little fixes and maybe it helped... Hmmm... I also uninstalled and re-installed with the database fix for the user table.

Thank you.
Alexis