The real differences between page, story, and blog are behavioural. Permissions, display settings, and default URLs (/blog and /blog/uid in the case of blog.module) are the issues. The ability to easily slice-and-dice stuff like 'latest content' listings for specific tyes is one of the reasons I'd love to see something like views.module (though not views_ui.module) eventually rolled into core. Providing JUST the backend features would allow module developers ot include that kind of functionality in a way that's relatively 'transparent' to end users. Advanced users could easily override the views by installing views_ui.module. Or something like it. But that's another debate, I suppose. The point remains: Story, page, and blog content types are essentially identical. The only purpose they serve is to provide different behaviors in configuration, etc. --Jeff
-----Original Message----- From: Adrian Rossouw [mailto:adrian@bryght.com] Sent: Monday, May 01, 2006 2:06 PM To: development@drupal.org Subject: Re: [development] Time to remove poll module from core
On 01 May 2006, at 9:15 PM, Gerhard Killesreiter wrote:
cool idea. And let's rm archive.module and maybe blog.module too. :)
and what's the different between page and story module at the moment, anyway.