Hello
Thanks a lot for the new Open Atrium release. I learn a lot with this distribution and I was able to recover my changes with Features Override and everything works.
I would like to use the Administrator Menu that comes with the distribution, but it gives to me errors. With the version that you include, 7.x-3.0, if you enable it, you get in the modules page
Notice: Undefined index: name in admin_menu_theme_settings() (line 708 of /.../sites/all/modules/admin_menu/admin_menu.inc).
In their issue cue they say that they won't fix because the 'disable development modules' functionality has been removed in version 7.x-3.0-rc5
I tried to update, but then you get
Warning: strtr() expects parameter 1 to be string, array given in admin_menu_tree() (line 27 of .../admin_menu.inc).
In their issue cue they say that has relation with Fieldable Panels Panes and that a solution is committed in FPP, but Open Atrium doen't use the dev version. Here they say v7.x-1.6-beta1 Fieldable Panels Panes version is coming. So I hope that you can make the Administrator Menu useful.
I hope this report help to you. Thanks again
Comment | File | Size | Author |
---|---|---|---|
#13 | database_engine_convert.txt | 853 bytes | delacosta456 |
#7 | panopoly_core-admin-menu-conflict-2420281-7.patch | 735 bytes | dsnopek |
Comments
Comment #1
mpotter CreditAttribution: mpotter commentedThe Admin menu is actually part of Panopoly and not something used or supported in Open Atrium. Open Atrium uses the Navbar module to put the Admin menu as a dropdown menu on the left side of the screen via the button in the OA toolbar.
Comment #2
candelas CreditAttribution: candelas commentedThanks for your fast answer. Could you, please, change the issue to Panopoly? Thanks
Comment #3
candelas CreditAttribution: candelas commentedI just learned how to do it.
Comment #4
dsnopekThanks for the bug report!
To make this easier to look up later, here is the FPP issue which fixes the conflict with admin_menu:
#2146479: Conflict with Administration menu
This also relates to the issue to upgrade admin_menu:
#2412321: Update admin_menu to 3.0-rc5
I think this shows we need a Behat test for admin_menu - at the very least walking through the process of enabling admin_menu, disabling navbar and clicking on something. I just made an issue for that:
#2420679: Write Behat test for admin_menu
Comment #5
candelas CreditAttribution: candelas commentedI like Admin Menu because you avoid many clicks and waiting for pages to load, so I was using it to see if I had any problem or what they were to report (at the moment I study and Drupal is too complicated to be able to fix such a thing). It has also conflict with OA toolbar, as I reported in Toolbar admin button broken on mobile screen Thanks for your interest to fix this :) and congratulations for being a father ;)
Comment #6
dsnopekI think the solution to this is adding the FPP patch to panopoly_core.make. I did a quick test to see if it'll apply, and it does with some fuzz (although, I didn't try using
drush make
) to do it. Here's a patch so I can test this with Travis-CI!EDIT: Here is the Travis-CI build: https://travis-ci.org/dsnopek/panopoly/builds/51087458
Comment #7
dsnopekBah! Rolled that patch against the wrong branch. Here's a new one.
EDIT: Here's the Travis-CI build: https://travis-ci.org/dsnopek/panopoly/builds/51103498
Comment #8
dsnopekOk! That Travis-CI build shows that the patch applies to our FPP and that it doesn't break anything our automated tests test.
I just tried admin_menu 3.0-rc5 and can reproduce the problem (the notice appears on module install) and confirm that the patch fixes it (the notice no longer appears after disable/enable).
This issue, of course, depends first on upgrading to admin_menu 3.0-rc5:
#2412321: Update admin_menu to 3.0-rc5
Comment #9
dsnopekComment #10
dsnopekCommitted!
Comment #13
delacosta456 CreditAttribution: delacosta456 commentedHi
On my own side this is what help me to fix admin_menu appearing and disappearing (it also work for non-panopoly distribution):
1: i update all table Engine from InnoDB to MyISAM with the php file attached (database_engine_convert) by loading it in browser
2 : Flush all cache with drush
May be it will help.