While Toolbar Core is okay, there are other very popular replacements to it, such as admin_menu, which Toolbar Core was based on, and admin. By making Toolbar Core dependency of OpenPublic Defaults, it requires end users to hack that module in order disable Toolbar and/or enable a Toolbar replacement, if they so choose. The same can be said for Overlay for those end users who do not like the Overlay, which many find to be especially cumbersome during development.
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | removetoolbar-1093692-0.patch | 1.87 KB | pedrorocha |
| #14 | openpublic_defaults.tar_.gz | 168.8 KB | pedrorocha |
Comments
Comment #1
g76 commented+1 just my personal preference, but I use admin and no overlay
Comment #2
Russell Mann commentedBump. Plz OP devs, remove the dependency.
Comment #3
jpoesen commented+1
Comment #4
alex ua commented+1
Comment #5
seanrJust wanted to add that the Overlay dependency may actually cause 508 compliance issues.
Comment #6
Russell Mann commentedThat's a lot of compliance issues! (g)
Try this SQL:
UPDATE system SET status='0' WHERE name='overlay';
Comment #7
Snugug commentedAs of the August 19th beta2 version of OpenPublic, there are still tied to the OpenPublic Defaults feature. Why?
Comment #8
warpdog212 commentedHow can the Toolbar and Overlay dependencies be removed? I'd like to implement CIVICRM but so many areas of the OpenPublic installation profile are hard-coded it is extremely difficult.
Comment #9
Snugug commentedWarpdog, I would not suggest trying to implement CiviCRM on top of an OpenPublic (or really any distro). If you want/need to use CiviCRM, I'd highly suggest installing it on a vanilla Drupal install and tying into it using Civi's API system.
Comment #10
Snugug commentedAlso, to more directly answer your question, I believe http://drupal.org/project/ftools allows you to remove individual pieces from a feature, which would allow us to remove the dependencies of Overlay and Toolbar ourselves, then disable them.
Comment #11
warpdog212 commentedThank you for the reply Snugug. Bit disappointed about the CIVICRM integration. I read the FAQ on http://community.openpublicapp.com/site-page/faqs regarding CIVICRM and hoped that that path had been explored. Will give the ftools a try and let all know how it goes.
Comment #12
bcobin commented@warpdog212
The FAQ is out of date. It says that a D7-compatible version of CiviCRM isn't available; 4.0 has now been out for some time. I've installed 4.0 on OP, but haven't messed around with it too much yet; I think it would be worth a try.
+1 on the Toolbar and Overlay dependencies being removed - I really miss my nice dropdown menus...
Comment #13
bcobin commentedI tried installing ftools and in D7 it wasn't apparent how to remove dependencies - besides, they recommend only using it locally. In the meantime, workaround is to remove overlay permissions for superadmin (clear caches after you do); that seems to make things much better.
Comment #14
pedrorocha commentedGuys, maybe create a new issue about CiviCRM could be better.
About the Overlay and Toolbar, they are great, but aren't functional dependencies for Open Public, so each site maintainer should be able to disable them and use other admin modules, if desired.
Overlay, from what i looked right now, isn't a dependency, being checked with module_exist() in every place.
For the maintainers, the patch to be aplied is attached.
For the sitebuilders that doesn't know how to apply a patch, the feature Open Public Defaults is attached too.
Comment #15
j0rd commentedThere's a field attached to the user profiles called something like "Use the overlay for administrative pages." where you can disable the overlay on a per-user basis.
For me, this works, although I don't much care for the overlay module all together and would like to option to remove it for everyone.
I second this feature request.
Comment #16
hefox commentedoverlay depedency is gone as far as I can tell.
Should toolbar dependency be moved to profile? Can use features exclude to prevent it from being added to permission feature but still export the permission.
Comment #17
hefox commentedComment #18
hefox commented