Allow for the ease of use and integration of seperate blog projects with drupal to streamline core code, and to allow maximum of choice, as there is for media gallery implementations & file repository implementations.

Comments

magico’s picture

magico commented
Version: 4.7.2 » x.y.z

I would like to understand better this idea!

rickvug’s picture

rickvug commented

I also would like to understand what you are wanting. "Seperate blog.module as a seperate project" almost sounds like you think that the blog module should be removed from core. Or maybe that's just me reading into your message and uncovering my own biases :)

grymwulf’s picture

grymwulf commented

Yes removing it from the core is the general idea. Many times I see that users are trying to use Drupal as an over-engineered blog, vs a true content management system. IMO it would be better to set up blog.module as a wrapper to allow presentation of a pure-blog package, or to use it as a mini-blog.

Also the following should be allowed to change: the default name/path etc, which isn't allowed as it is in the core.

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Active » Closed (won't fix)

Dries has indicated he doesn't want to remove modules from core for thr time being. Maybe you should submit patches to the core blog module.