CiviCRM Community Forums (archive)

Anyone out there use this Administration Menu module and notice that it cuts off the parameters from the CiviCRM links in the drop down menu.  Of course this causes all kinds of nonsense and confusion on certain CiviCRM pages when you can't reset the search results by clicking Find Contacts again.

Solution anyone?  Contacted Administration Menu people and they haven't responded yet.

Hi I thought I would revisit this issue.

Some folks in the CiviCRM community speak highly of Administration Menu (admin_menu) module, but the fact that it removes the &reset=1 from the links means that Contact and Group searching becomes completely unusable if accessed through the Administration Menu by a regular non-programming user who doesn't understand manual URL manipluation (aka copying and pasting &reset=1 every darn time).

I wonder if people who like Administration Module with CiviCRM even use the admin_menu to do Contact searching and are aware of this problem?  It boggles my mind.   In my opinion CiviCRM should not have an admin_menu if the links to Find Contacts , etc  .... don't work because they can never be reset unless manually editing the URL line is done. (which is silly and something a non-technical user doesn't get)

Is integration of CiviCRM with the admin_module optional?  Can we turn it off through CiviCRM?

Because the CiviCRM links in admin_module don't work, I would like to have admin_module active for everything BUT CiviCRM.

I contacted the curator of admin_module and he appears completely unaware of CiviCRM's existence or this problem and even suggests that CiviCRM links don't belong in the Admin Module in the first place:

I don't use CiviCRM, so I am unable to debug this.

Also, I don't quite understand this issue. admin_menu contains administrative links only. The path of the links you mentioned do not start with admin/*, so they should not be contained in the menu.

http://drupal.org/node/425866

So...any ideas?  Can I remove CiviCRM links up in the Admin Menu?

BTW for 2.3 we are looking at implementing a top-bar drop-down menu for CiviCRM - which will probably "replace" the admin menu when you're viewing a CiviCRM page or form (so this may become a moot point).

If at all possible, I think our users would prefer a combined menu to two separate top-bar dropmenus. The distinction between CMS and CRM functionality is totally opaque to most mortals, and IMO should not be made explicit in the GUI.

(Of course, I understand why CiviCRM would want a menu of its own, rather than depending on the admin_menu module for Drupal only. But to lose that functionality for people already using the otherwise excellent admin_menu would be a real shame.)

I'm in the converse role - programmer first, CiviCRM user rarely - and I concur that many bugs don't get reported. I think it's not so much that few people are seriously using CiviCRM, and rather that the users of a complex tool are quick to learn and then sidestep its intricate behaviours, rather than engage with the programming trolls who will grunt their terrible grunts and interrogate them for details like "steps to reproduce".

I say that as one of the coders who has to occasionally twist a user's arm for those most valuable details. If we technicians aren't careful to assist them in making good bug reports, we run the risk of scaring the best source of bugs away from trying to report them in future...

Interesting thoughts, yes sometimes there is a disconnect between programmer and user - I guess this is the case for all software.   Thanks for making the patch.  If I can offer something to community perhaps it's to help bridge that gap.