Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Just upgraded to Views 6.x.2-7 and this error appeared on a number of my pages which are built using views but not all pages built using Views.
"warning: preg_match() expects parameter 2 to be string, array given in /home/website/public_html/test/includes/bootstrap.inc on line 777."
Downgrading to Views 6.x.2.6 clears the problem.
Error appeared for all users on my site.
Drupal 6.14
MySQL 5.1.33
PHP 5.2.9
All contributed modules are up to date as of today with the exception of Views.
Posted this also on http://drupal.org/node/320145
What other information can I provide?
Comments
Comment #1
dawehnerDo the following code into before 777
You need devel for this.
Comment #2
robbertnl CreditAttribution: robbertnl commentedSame here
Comment #3
leevester CreditAttribution: leevester commentedAfter adding the code from #1 and enabling the Devel module, I followed one of the errors to the views_plugin_display.inc. According to the manifest it should be v 1.27.2.4. When I checked the file, it reads v 1.27.2.1 2009/10/28. I compared this file to the CVS repository, it is 1.27.2.1.
Thinking that I might have messed up with the upgrade, I downloaded Views again and unpacked it into another directory. The 1.27.2.1 is in still there.
Tried patching the file up to 1.27.2.4 but my problem still exists.
If you can give me a hint on how to store the Devel Error messages for you, I will be glad to send a couple your way, if you think it will help.
Comment #4
dawehnerIn which line is this called?
Comment #5
robbertnl CreditAttribution: robbertnl commentedThe fieldvalues are also empty in combination with gmaps. Reverting to views 6.x-2.6 resolves both problems (warning message and empty fields).
Comment #6
merlinofchaos CreditAttribution: merlinofchaos commentedAhh this is another case of styles needing to be updated.
Comment #7
tavaressimon CreditAttribution: tavaressimon commentedI have downgraded to 6.x.2.6 but I still have the same issue.
Comment #8
robbertnl CreditAttribution: robbertnl commentedStrange, did you try changing the view styles / making a new view?
Comment #9
colorado CreditAttribution: colorado commentedhttp://drupal.org/node/525036 fixed it for me, with no side effects
Comment #11
leevester CreditAttribution: leevester commentedJust got back to this and http://drupal.org/node/525036 also fixed my issues as well.