Question to Community: Magento Modules

[Tiurnikova]

Hi there,
One of the goals of Magento 2 is to reduce dependencies between modules and make it easy to disable them. Some modules have already been cleaned up (Catalog, Checkout, Shipping, Sales, Payments). Please, check last dev versions.

We are considering the following modules as possible candidates for the further work.
Please, share your thoughts on given priorities. Which modules are the most critical?

• Log
• Logging
• AdminNotification
• Rss
• Backup
• Tax
• Weee
• SalesArchive
• VersionsCms(CmsHierarchy)
• Bundle
• Downloadable
• Rating
• Review
• GiftMessage
• Rma
• ProductAlerts
• SalesRule
• CustomerSegment
• Wishlist
• Newsletter
• Reports
• CategoryPermissions
• Captcha
• CatalogSearch
• Compiler
• Connect
• GiftRegistry
• Poll

Thanks

[SchumacherFM]

All of them. But no worries if you can't make it in time. I will port https://github.com/Zookal/magento-mock to Magento2 if necessary.

Priorities depends really on the project.
But here my list.

1. Newsletter
2. Connect/Backup
3. AdminNotification
   ...

[jpratt]

I would imagine those that are not is use by most would be great to easily turn off:

1. Weee
2. Downloadable
3. RMA

[Vinai]

I think the following modules are not used in many instances, so it would be good to be able to remove/deactivate them.

In order of preference:

• Newsletter (almost noone uses it - all use mailchimp or another provider)
• RSS
• CategoryPermissions
• GiftRegistry
• Downloadable
• Wishlist

The admin notification module is often turned off because it slows down the admin login. If that where changed, I don't think people would mind it so much.

[gfxguru]

We need a workflow!

[mzeis]

Short version:

Make disabling easy for these modules: Log, Logging, AdminNotification, RSS, Compiler, Newsletter.

Long Version:

My experience from our projects:

• Log / Logging: make visitor logging to the database optional. As long as the data in the log database tables cannot be used / analysed more easily in the backend it should be easy to turn of the logging of page visits etc.
  The logging data which now is saved in system.log / exception.log is better readable and analysable in a structured form so it would be nice if it could be saved in the database as it was implemented in https://github.com/firegento/firegento-logger.
• AdminNotification: add an option to disable the notifications globally or on a user basis. We have only one merchant that really wants to read the messages. Normally we act on any notifications and/or updates directly and we know about it from Twitter, Mail, RSS, ... before we see the message in the admin notifications so it's really not necessary that we have to click away the messages in every single admin dashboard.
• RSS: remove/disable it. We never used it.
• SalesArchive: would be awesome to have in CE.
• VersionsCms(CmsHierarchy): hierarchic menus in CE would be very important. Is this about the EE functionality? If so: I can understand if you are not willing to implement a rich CMS functionality into CE I can understand it from a marketing stand point. On the other side, the current CMS functionality in CE is in no means a replacement for a CMS. At least it should be possible to creat hierachical CMS content and create custom navigation trees vor CMS pages (separate from the category navigation).
• Compiler: remove/disable it. We never used it because it caused more problems than it did help.
• Newsletter: remove/disable it. As Vinai pointed out: if you want to send Newsletters we always do it using external providers. It would be better to invest into built-in integrations with external providers than to maintain a module which is not useful for any not-tiny store.

[kbariotis]

+1 for @mzeis !! Well said.

From my experience:

• Logging : Never Used it
• AdminNotification : Never Used it
• Rss : Never Used it
• Backup : Never Used (cPanel is making the hard work)
• Tax : There have been a lot of situations that we didn't use
• Bundle : Never Used it
• Downloadable : Never Used it
• Rating : Should be easy to disable it
• Review : Should be easy to disable it
• GiftMessage : Never Used it
• ProductAlerts : Never Used it
• Newsletter : I would say that it would be good to leave this inbrowser editor for email templates as it is far from easy and no customers can use it. Keep a mini version without templates where emails consist only by text and a logo. And only if the developer wants to can implement a 'phtml' template file.
• Reports : We are using it but i would say that needs work. See a lot of these can already seen in google analytics. Make something that can't find in GA.
• Captcha: Never Used it
• Connect : Never Used it. There is a big possibility that system would break. We only allow developers to play with extensions.
• Poll : Never Used it

[tzyganu]

There are a lot of modules I never used, but that does not mean they are not useful. Like Downloadable, Captcha, ProductAlerts, GiftMessage.
But please do what ever it takes and detach the compare products functionality from the Log module. Let me disable the log module if I want to. I can say that 100% of the clients I've worked with never needed this.
I added an unanswered question for 1.x, asking why is this needed (http://magento.stackexchange.com/questions/30801/why-is-the-compare-functionality-linked-to-the-logvisitor-id). If you plan to port the same thing on 2.x at least give a reason.

[Tiurnikova]

Thank you for your feedback.
@stakisko some of the modules you mentioned are already removable, like Rating, Review; Poll was completely removed from M2.
@tzyganu , we are working on Log module right now. Check release updates in 2 weeks, it will be easy to disable and remove this module.

Thanks