Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By dzrobarge on
is there anything wrong with having a whole bunch of modules enabled? i'm so new i don't know what i need or don't need so I figure enable it just in case....
Comments
Enabled based on the Core
Enabled based on the Core content? No, you can have them all enabled and it should run fine. I mean, assuming your website allows it. Obviously, it is best to turn off the modules you don't need for performance reasons, but if they don't get called for any reasons, it shouldn't affect overall site performance or make your website collapse due to too many modules.
I personally went on a module spree and downloaded tons on a test site and had... I don't even know how many I had. I enabled them all and worked with them and it ran fine.
Are you currently experiencing some sort of issues, or is this just precautionary?
Also, I could be wrong--I've been using Drupal extensively, but only for the past week or so. I've probably just scathed the surface of the system.
No issues so far. Just
No issues so far. Just thinking that maybe, since modules are not automatically enabled, that there might be a reason to not turn them all on.
"module spree" - yes I did that too! I removed a ton - going to wait to expand after I learn the basic ones. Having a hard enough time with core, cck and image.
I get errors on a bunch of
I get errors on a bunch of them that I'm not quite sure about. All the same error which locks up my site until I manually delete the module from the /drupal/modules folder, which probably isn't code but can't be avoided. Have you received anything similar?
I can't figure it out...
certainly recommended to only
certainly recommended to only have what you need.
My site has a pile installed, but it doesn't seem to affect performance. Good to remember that performance is MUCH better when not logged in.
if something goes wrong...
if something goes wrong... having fewer enabled modules will make it easier to find the offending module. This is true specially with contributed modules: two modules may work fine on their own, but not when both are enabled. Personally I work it the other way round: start with nothing, and enable a module only after I figure out what it does, and why I need it.
Agreed, it made it easier to
Agreed, it made it easier to find the solution to a bunch of my problems. But I found it easier to start with tons of modules on my module-spree, figure out 80% of what something does, then go back and work from the start. Just my method, maybe encountered more trouble, but saved some time in the long run, I hope!
What's messed up is it takes
What's messed up is it takes around 35+ modules just to have a decent functional Drupal (not as good as wordpress but decent). However, really it takes around 70-75 modules to do it right and that slows the module page down to a crawl because Drupal has to scan every single module. I have around 70 so far and many are to make the admin function better.