I just installed the 2009-Aug-06 dev version of Boost. I am getting two errors when adding new content or viewing my blogs (blogs/[uid]). I do not see the error on other pages. The error is:

* warning: mysqli_real_escape_string() expects parameter 2 to be string, array given in /home/xx/public_html/xx.com/includes/database.mysqli.inc on line 323.
* warning: mysqli_real_escape_string() expects parameter 2 to be string, array given in /home/xx/public_html/xx.com/includes/database.mysqli.inc on line 323.

The errors disappear if I disable the Boost module. I only get the errors when the Boost: Pages cache status block is enabled and displayed in my theme.

I did not have the errors before when I was running Boost 6.x-1.0-rc1.

Comments

mikeytown2’s picture

Status: Active » Needs review
StatusFileSize
new1.74 KB

I can reproduce the bug, it happens on login as well... it has something to do with _boost_get_menu_router(), which is code I lifted from http://api.drupal.org/api/function/menu_get_item

found the problem, here is the patch

Tally’s picture

Status: Needs review » Needs work

I can confirm that the above error is gone after installing the patch.

But . . . now the Boost block does not show the proper page/scope info. The block shows the following for every page, not just the ones that previously had the error:

Page ID
- 0
Content Type
- NULL
Content Container
- NULL

The patch code inserted at line 1803 tests $ancestors for being an array, but that variable is always an array (at least, as far as I can tell with the devel module). This means that none of the original code below the end of the if statement is executed.

mikeytown2’s picture

Status: Needs work » Needs review
StatusFileSize
new1.95 KB

Thanks for checking. I can only reproduce the bug on non subdir installs, so this is a sneaky bug...

Tally’s picture

Status: Needs review » Reviewed & tested by the community

I'm running Drupal 6.13 in the root with a multi-site setup.

Applied the patch and the Boost config block displays the correct values, and the original error does not show up. :)

Thanks.

mikeytown2’s picture

Status: Reviewed & tested by the community » Fixed

committed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.