Hello,

I've got a multisite Drupal install coupled with SVN to accomodate multiple developers on the same project. The same site using the same DB can be accessed via different paths (working copies) so the caching mechanism of this module doesn't play well with this set-up. Admin_menu basically caches the path of the first-accessed working copy (site path) and while another working copy is accessed, the menu paths point to the wrong site path.

Can there be a setting in the module settings page to disable caching of the module?

I've used SimpleMenu for a while and just tried this module out, but I'm concerned what will happen when the two modules are merged (Drupal Menu Renderer) particularly with the caching problem.

Thanks

Comments

sun’s picture

Component: Miscellaneous » Code
Category: feature » support
Priority: Minor » Normal
Status: Active » Fixed

As with any other module in Drupal, you should setup separate cache* database tables for each domain via settings.php, using different table prefixes for each domain. Admin Menu certainly isn't the only the module that outputs cached links. See sites/default/settings.php for more information about multi-site setups and database configuration.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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

brad.bulger’s picture

We are having the same problem and using database prefixes is not an option, as we need to all be using the same database for multiple reasons.

What's odd, though, is that if I look at the page source, I see the correct current path. But when I click on the link, it goes to the incorrect, old path. Navigating around on the site doesn't change this. Any ideas on what might be going on there?

sun’s picture

Status: Closed (fixed) » Fixed

I guess, by "path" you meant "domain". If you have different base paths, modules, menus, OR user permissions on each domain, you must use different table prefixes for your cache tables. There is no workaround for that. However, please note that you only need to prefix your cache tables, not all tables.

If the base path, modules, menus, and user permissions are the same for all domains, then the occurring bug is not related to admin_menu. You should then check the issue queue of the module you used to split your site into multiple sites.

If you did not use a contrib module to separate your site into multiple sites, and you have a different base path on each site, you must use different table prefixes for your cache tables. That is, not only because of admin_menu. All links that are output from Drupal will potentially contain the wrong base path.

brad.bulger’s picture

no, i meant "path" - different base_path values, same database. but prefixing the cache tables only will work fine. i had added an extra component to the cache ID value to get around this problem, but as you say, the prefix will fix more general potential problems. thanks.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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

jonskulski’s picture

For what it's worth: here is a blog post where I explain the process:

http://www.chapterthree.com/blog/jon_skulski/admin_menu_multiple_develop...