Core Content Types should be defined like others

[RandyWalker]

For consistency, the core content types should be defined separately like extra content types.

[ringmaster]

Habari is blogging software. The core content types facilitate this purpose. Extra content types are just that -- extra. For that reason, the extra features are not core, and the innate features are core.

[RandyWalker]

Right, but just because they ship as part of core is no reason why they're created in an entirely different way. We don't treat core plugins or core themes any differently than extra plugins or extra themes (other than a different location).

[michaeltwofish]

Content types are created with a single line of code, whether it's in the installhandler or in a plugin. I'm not sure what change you are proposing.

[RandyWalker]

I'm just saying that "entry" and "page" should have a file like this:

http://trac.habariproject.org/habari-extras/browser/plugins/publish_quote/trunk/publish_quote.plugin.php

that 1) adds the content type 2) adds all the right fields

why? Consistency and customization.

[skippy]

Entry and Page do not require additional files. They are defined during installation. They are (currently) non-configurable content types, and may not be disabled. Marking this as wontfix.