With the "Do not store the cache file path in the database" option checked (I run Domain Access) it appears Boost is having issues knowing my table prefix.

I'm noticing a TON of logs to watchdog to the effect of "Table doesn't exist...". When it lists the table in question (boost_cache, boost_crawler, etc.) it is doing so without the prefix, which is obviously preventing it from finding my tables.

I have all of my drupal tables prefixed with drupal_. I fixed this by manually applying my prefix to a lot of the multi functions in boost.module, but now I'm noticing other major errors like with the crawler and things of that nature.

If you need any more info please let me know.

CommentFileSizeAuthor
#1 boost-631452.patch1.72 KBmikeytown2
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikeytown2’s picture

Status: Active » Needs review
FileSize
1.72 KB

I'm going to guess that PHP is goofing on the variable replacement with {$table}. Try this patch, it uses {" . $table . "}.

Jim Kirkpatrick’s picture

Am also getting lots of "table boost_xxxx doesn't exist" errors, using "drupal_" as a table prefix.

Have applied the patch in #1 and am testing - will report back, thank you Mike.

mikeytown2’s picture

Status: Needs review » Fixed

committed
Please Let me know if this doesn't fix the problem. You can grab the code in todays dev when it comes out in about an hour from now.

Status: Fixed » Closed (fixed)

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