Errors on my content creation page, but error coming from coresearches module

jrefano - February 25, 2009 - 23:12
Project:Addresses
Version:6.x-1.05
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active
Description

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.

#1

andersonmh - March 14, 2009 - 19:47

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

#2

kriskd - March 19, 2009 - 18:00

Just got this error as well.

#3

selwynpolit - March 27, 2009 - 20:02

Me too. It would be nice to use this.

#4

Iowagirl - April 2, 2009 - 23:16

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

#5

torstenzenk - April 14, 2009 - 04:57
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.

#6

imp7 - October 15, 2009 - 02:10

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.

 
 

Drupal is a registered trademark of Dries Buytaert.