Category Browser is not configurable on Administer > Site Building > Menus

Sure! I'll be happy to give more information.

I've attached some screen shots to this post. I'll describe what the screenshots are below, but know that in all cases I've done everything I know to make sure that the page I'm seeing reflects what Drupal thinks it is -- Refresh, Clear the cache through the Devel module, etc. Also, these screenshots are 100% reproducible, so let me know if you need more. In all the screenshots, the Category Browser has weight -10 to make sure it floats up to the top of the navigation menu and configuration section. (The next-lightest item, "Database queries," has weight 0.) I added the red boxes highlighting the Category Browser menu item myself post-screenshot, so no worries there.

If I use the stock taxonomy_browser code, then the /admin/build/menu page looks like the attachment admin-menu-screenshot-before.png. Note that the "Category Browser" menu item is configurable and enabled, but the Category Browser menu item does not appear in the navigation menu. (Again, this is not due to stale data. I refreshed the page and cleared the Drupal cache.)

If I use the stock taxonomy_browser code, then the / page looks like the attachment admin-home-screenshot-before.png. The Category Browser menu item appears in the navigation menu, but it does not float to the top like it should.

Now, if I make the following change to taxonomy_browser code (thanks for the suggestion on diff args -- you're right, that is much better):

[~/public_html/modules/taxonomy_browser] $ diff -u -p taxonomy_browser.module.orig taxonomy_browser.module
--- taxonomy_browser.module.orig        2008-05-26 23:38:42.000000000 -0500
+++ taxonomy_browser.module     2008-05-27 22:52:59.000000000 -0500
@@ -28,7 +28,7 @@ function taxonomy_browser_menu($may_cach
       'access' => user_access('administer site configuration'),
       );
   }
-  else {
+//  else {
     $items[] = array(
       'path' => 'taxonomy_browser',
       'title' => t('Category Browser'),
@@ -39,7 +39,7 @@ function taxonomy_browser_menu($may_cach
       'type' => MENU_NORMAL_ITEM);

     drupal_add_css(drupal_get_path('module', 'taxonomy_browser') .'/taxonomy_browser.css');
-  }
+//  }

   return $items;
 }

...then the menu and and home pages look like admin-menu-screenshot-after.png and admin-home-screenshot-after.png, respectively. On the menu page, note that the Content Browser menu item is configurable and appears at the top of the navigation menu. Similarly, the Content Browser menu item appears at the top of the navigation menu on the home page as well, as it should.

So, I'm definitely seeing weird behavior with the stock code, and this code change fixes it. Now, you know more about why that menu is not served when $may_cache is true -- I have experience in development, but I'm still new to the Drupal scene -- so it may be that this is a fix, but the not the right fix for this issue.

Also, here's a list of the modules I have installed on my site, in case that's useful:

[~/public_html/modules] $ ls -l
total 208
drwxr-xr-x 52 sigpboo7 sigpboo7 4096 May 27 23:04 ./
drwxr-x--- 12 sigpboo7 nobody   4096 May 26 20:55 ../
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 aggregator/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 May 26 14:33 amazon_filter/
drwxr-xr-x  3 sigpboo7 sigpboo7 4096 May 26 14:15 amazontools/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Oct  9  2007 asin/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 May 27 01:07 block/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 blog/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 blogapi/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 book/
drwxr-xr-x  4 sigpboo7 sigpboo7 4096 Apr 29 08:30 cck/
drwxr-xr-x  3 sigpboo7 sigpboo7 4096 Jan 28 18:10 color/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 comment/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 contact/
drwxr-xr-x  5 sigpboo7 sigpboo7 4096 May 25 22:39 devel/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 drupal/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 filter/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 forum/
drwxr-xr-x  5 sigpboo7 sigpboo7 4096 May 25 22:14 geshifilter/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 help/
drwxr-xr-x  4 sigpboo7 sigpboo7 4096 Apr 13 19:05 image/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Feb  6  2007 image_filter/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 legacy/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 May 21 12:45 link_node/
drwxr-xr-x  3 sigpboo7 sigpboo7 4096 Dec 11 22:20 links/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 locale/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 menu/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 node/
drwxr-xr-x  3 sigpboo7 sigpboo7 4096 Mar  7 07:55 node_type_filter/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jun 18  2007 override_node_options/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 path/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 ping/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 poll/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 profile/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 search/
drwxr-xr-x  3 sigpboo7 sigpboo7 4096 May 25 20:58 service_links/
drwxr-xr-x  4 sigpboo7 sigpboo7 4096 Jul 14  2007 smileys/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 statistics/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 system/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Dec 12 07:55 tac_lite/
drwxr-xr-x  3 sigpboo7 sigpboo7 4096 Feb 10 13:55 tagadelic/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Feb 19 07:50 tagadelic_views/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 taxonomy/
drwxr-xr-x  3 sigpboo7 sigpboo7 4096 May 27 22:52 taxonomy_browser/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 throttle/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 tracker/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 upload/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 May 27 01:28 user/
drwxr-xr-x  4 sigpboo7 sigpboo7 4096 May 26 23:54 views/
drwxr-xr-x  3 sigpboo7 sigpboo7 4096 Feb 19 07:50 vocabperms/
drwxr-xr-x  2 sigpboo7 sigpboo7 4096 Jan 28 18:10 watchdog/
drwxr-xr-x  4 sigpboo7 sigpboo7 4096 Jun 14  2007 websnapr/

Most of those modules are enabled, but not all of them. (For example, websnapr is not enabled.) If there are any modules here in particular whose enabled status you're curious about, let me know and I'll look it up.

The website I'm having the trouble on is here if you need to see it for some reason.

I hope this information is useful. Again, thanks for a great module. Let me know if there's any other way I can help!

Absolutely, no problem.

I disabled and re-enabled the module; the 'Category Browser' menu entry still doesn't appear when in Administration -> Site Building -> Menus. I applied my change and the menu entry showed up. I reset the entry; it still showed, which is good. I reverted to the stock code, and the menu entry disappeared again.

Honestly, I'm only running a small-time personal site. I can set up an admin access account for you if that's helpful. Would that help you to run this to ground?

That's interesting. I was reading up on Drupal menus over lunch to figure out whether or not this menu really should be cacheable and I didn't pick up on that nuance. Is it true that you you can't cache a menu if specific permissions are required to see it?

Fortunately, that's a testable hypothesis. I'll run a quick experiment when I get home to run that, unless someone here points me to documentation that covers that particular detail about menus.

Also, after reading up on menus, I understand that the patch I've submitted is wrong. The patch returns the menu regardless of the value of $may_cache, which means that the menu item is likely to be returned twice. Obviously, that's not the right thing. If the menu should be cacheable, it should just be moved from the else up to the if. I'll submit another patch later, hopefully tonight.

The problem I'm having is that the "Category Browser" doesn't show up in the menu admin screen with the stock module definition, so I can't configure it. So long as we can get the Category Browser to show up on the menu admin screen, I'm happy :)

I think a good way to determine The Right Thing here is to look at similar modules that expose menu items that do appear in the menu admin screen and see how they handle caching. I should have some time to do that tonight, and I'll post what I find.

Junyor, I appreciate your input on this issue, and NancyDru thank you for being so on top of this. I'm not used to getting this much developer attention unless it's my own :)

Right. Sorry for confusion. I meant that last bit just for NancyDru.

Sorry for the radio silence on this issue.

NancyDru, I've just installed the latest version of Taxonomy Browser, which is 5.x-1.2, so I'm not upgrading. However, what Junyor's describing is very similar to what I'm doing. However, "Require Permissions" is not enabled on Taxonomy Browser for my site, but I still cannot see the "Category Browser" menu item in /admin/build/menu.

The issue that I'm having is that the "Category Browser" menu item is not configurable on /admin/build/menu, so I can't disable it.