Stupid question about "yellow dots"

[Ajeh]

Yellow dot means either you have a configuration issue or that there is a Zone or filter set on the module ... or, you could have the module Installed but set to Disabled ...

NOTE: modules that are set to Disabled should be REMOVED and not left as Installed and marked disabled ...

[Ripper]

Ok, that's it... There is a zone set. Thanks.

[RodG]

NOTE: modules that are set to Disabled should be REMOVED and not left as Installed and marked disabled ...

Hi Linda, (Happy new year)
I don't recall ever seeing this recommendation before. Is there a reason for it, other than the fact that modules that have been removed are less likely to cause compatibility/security issues than those that have merely been disabled?

The reason I ask is that I tend to install a lot of modules on our development server (for testing/evaluation purposes) and unless they mess things up, if I choose to discontinue their use I simply disable rather than remove (especially the postage modules). I do this because it makes it easier to re-enable again at another time for further checks if required.

I've never found this to be an issue, but as a result of your recommendation I'm now wondering if there are any issues or traps that I'm unaware of in this regard?

As a general rule, I do agree with you, unused modules are best removed rather than disabled.

Cheers
Rod

[DrByte]

Rod,
It's not as much an issue for shipping modules, and especially on a Development-only server, but when it comes to payment modules, we've been strongly recommending Remove instead of Disable for a couple years now due to a quirk that can cause a "disabled-but-installed" module to get triggered unexpectedly and without explanation on intermittent occasions.
We hope the quirk is fixed in the upcoming 1.3.9 and 2.0 versions.

Anyway, we have now completely digressed away from the original topic of this thread.

[RodG]

when it comes to payment modules, we've been strongly recommending Remove instead of Disable for a couple years now due to a quirk that can cause a "disabled-but-installed" module to get triggered unexpectedly and without explanation on intermittent occasions.

Thanks.

Anyway, we have now completely digressed away from the original topic of this thread.

I'm good at that

Cheers
Rod