I've got several sites setup to run from the same Drupal core code base.
When I apply the patch, included as part of this module, all sites which do not have Path Cache installed display the following user warnings:
* user warning: Table 'my_site_database.cache_pathdst' doesn't exist query: SELECT data, created, headers, expire, serialized FROM cache_pathdst WHERE cid = 'js/admin_menu/cache/6d030bb2624729e3e353ddb610fecceben' in /var/www/drupal-6.14/includes/cache.inc on line 26.
* user warning: Table 'my_site_database.cache_pathdst' doesn't exist query: UPDATE cache_pathdst SET data = '', created = 1263148779, expire = 1263191979, headers = '', serialized = 0 WHERE cid = 'js/admin_menu/cache/6d030bb2624729e3e353ddb610fecceben' in /var/www/drupal-6.14/includes/cache.inc on line 109.
* user warning: Table 'my_site_database.cache_pathsrc' doesn't exist query: SELECT data, created, headers, expire, serialized FROM cache_pathsrc WHERE cid = 'nodeen' in /var/www/drupal-6.14/includes/cache.inc on line 26.
* user warning: Table 'my_site_database.cache_pathsrc' doesn't exist query: UPDATE cache_pathsrc SET data = 'node', created = 1263148779, expire = 1263191979, headers = '', serialized = 0 WHERE cid = 'nodeen' in /var/www/drupal-6.14/includes/cache.inc on line 109.
etc, etc... for each of the files in the cache
There should be some kind of exception which tests if the site has the Path Cache module installed before assuming the database tables exist.
Comments
Comment #1
crea commentedsubscribing
Comment #2
crea commentedAttaching updated patch (not a patch to patch LOL). Basically I wrapped every cache function call in a module_exists('pathcache').
Comment #3
jvandyk commentedYou've modified the Drupal core code with a patch. But now you want some other sites, using the same code, to not run this patched code? I don't think that situation is reasonable for support in the module. If you run multisite with a core patched by pathcache, all sites will need to run pathcache. (You could get halfway there by creating the two new cache tables the sites are complaining about but without the module enabled you'd miss cache flushes.)
Comment #4
crea commentedPlease note that this causes lots of errors when you install new site to the same multisite installation. If its that easy to fix, I see no reason to leave it broken.
Comment #5
mattdanger commentedThe included path.inc.patch does not account for new site installations on multisite environments. This causes new site installations to fail with the error described in the OP unless the installation profile is tweaked to install pathcache first.
crea's patch is a sufficient fix.
Comment #6
gbaudoin commentedComment #7
fabianx commentedD6 is EOL.