Closed (duplicate)
Project:
Devel
Version:
6.x-1.16
Component:
devel
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Apr 2009 at 22:50 UTC
Updated:
16 Apr 2009 at 13:36 UTC
I got this warning message after updated the following modules to the latest version: filefield_path-6.x-1.0.tar.gz, views-6.x-2.4,devel-6.x-116
I do not know which one cause problem, mainly happen when I try to do edit on content and content type (manage fields)
* warning: preg_match() expects parameter 2 to be string, array given in /Library/WebServer/Documents/shwaware/sites/all/modules/admin_menu/admin_menu.inc on line 244.
* warning: preg_match() expects parameter 2 to be string, array given in /Library/WebServer/Documents/shwaware/sites/all/modules/admin_menu/admin_menu.inc on line 244.
Comments
Comment #1
yched commentedWrong component, obviously.
This most probably comes from a broken 3rd party module, trouble is finding which one.
You'll have to be more specific on which exact pages trigger the error.
Comment #2
greenbeans commentedI'm getting this error too after updating Devel to 1.16. Presumably a bug in that module.
Comment #3
avpadernoI agree: it's more probable the error is caused by a third-party module.
Comment #4
fenstratSame as #2 after updating to Devel 1.16 - preg_match() warning: expects parameter 2 to be string, array given in admin_menu.inc on line 244
Comment #5
avpadernoI am moving the issue to the issue queue that seems more appropiate, basing on the last comments.
Feel free to move it if it doesn't seems the correct queue.
Comment #6
s.daniel commentedSame error after update. (In a multisite envoironment where devel is simlinked)
Comment #7
avpadernoI am changing the referring version to the last official release; is the issue still valid (I ask my apologies in the case I have not understood correctly what s.Daniel meant)?
Comment #8
greenbeans commentedCurrent version (version with problem) is 1.16, not 1.6 or 1.9.
Comment #9
avpadernoUsually, if the problem has been fixed in the latest official release, the users who have an issue with a previous version should pass to the latest official release.
In Drupal, when the maintainer fixes a bug with an official release, he must create a new official release, as it's not possible to commit the fixed code and keep the old version number.
What is the need to fix a bug if the users still use the bugged version?
Comment #10
greenbeans commentedPeople updating the metadata of this bug report misread a) the version number it was being reported against, and b) the latest version number of the module. The bug is being seen in the latest version (1.16). (See OP, #2, and #4).
Comment #11
Johnny vd Laar commentedThe devel module now returns an array instead of a string. the dev version of the admin menu has this solved so you should use the latest dev version of the admin menu to solve this
Comment #12
seaneffel commentedConfirming this last comment from Johnny. Updating to the 6.x-3.x-dev Administration Menu module put an end to this error message. Marking as fixed.
Comment #13
s.daniel commentedSeems to be fixed with 6.x-1.x-dev as well but 1.x dev introduces a new error: http://drupal.org/node/433016
Comment #14
EmanueleQuinto commentedCheck http://drupal.org/node/430374