Hello Josh,

Yep, it shouldn't. We are planning to upload these "non core" modules to http://stackideas.com/apps

Thanks Mark. Good to hear. Unintalling modules is not a big deal, but I know after a while it would take extra time and some folks won't even notice.

Noted

Just a heads up that the EasyBlog module still installs upon upgrade. Yesterday I specifically uninstalled the EB module, then upgraded to ES 1.2.7 using the launcher. The EB module is back.

As stated earlier, it should go onto the stackideas apps section rather than be built into ES.

Noted, thanks for the heads up on this Josh

The EB module is still in ES 1.2.8 as far as I know.

Hello Josh,

After discussing with the team, we think it's okay to include this module in the package. If the user doesn't want it, they can remove or not publish it.

Shouldn't the module come with EasyBlog instead? With each upgrade to EasySocial, the module returns.

Hello Josh,

Yeah but this particular module is accustomed to EasySocial's styling so that the listing blends in nicely with the items in EasySocial

Makes sense. However I think it would be best to "unify the module". Rather than having a EB latest module for ES and a EB latest module for EB, why not have them "combined"? I would have the recent EB module have a setting specifically for loading EasySocial styling. This would not only make the EasySocial package slightly lighter, but would save the stacked team work by reducing the need to maintain two modules. The unified one would be the only one that would need maintaining.

Not every user that uses EasyBlog has EasySocial installed

Right, which is why I proposed the styling as an option on the module. The ES styling could be disabled by default (two options, one being EB style, the other being ES styled).

Yep, we'll see what we can do about this