CMS Made Simple Forums

Why is CMSMailer present and MenuManager installed on a clean 2.0 install? Both of these modules look to be deprecated, which is shown if you navigate to the Module Manager after you're done with installation.

Wouldn't it be better, for new users especially, when these two modules would be left out directly on a clean install?

I noticed that as well.

From the 2.0 documentation it appears that CMSMailer was left intentionally:

Though a CMSMailer module exists as part of the core, it is now just a stub module without an interface. Its only purpose is for backwards compatibility with older code, and as such it is not installed by default for new installs. Improvements to the core page types.

Nothing about why MenuManager is still present.
Probably to not break upgrades to 2.0.

otopanne wrote:Probably to not break upgrades to 2.0.

Correct

Rolf wrote:

otopanne wrote:Probably to not break upgrades to 2.0.

Correct

But the MenuManager is even installed in CMS Made Simple, not just present in the Module Manager like CMSMailer.

Maybe this should be a feature request but just as there is logic in the install script present to install templates and demo content by default I would suggest leaving out these two modules on a clean install.

Still present on clean 2.1 installs, CMSMailer is just there and MenuManager is also installed.

tristan wrote:Still present on clean 2.1 installs, CMSMailer is just there and MenuManager is also installed.

Because if we would drop them from new installs it might break third party modules or methodes you want to install later...
When all (read most) modules are updated by their developers and CMSMS 1.x isnt supported anymore by the dev-team, we can decide to remove them from the package. Before that isn't smart!