When installing this module, you create a new node type. While this is convenient, it has its limitations:
- under Manage fields , after adding new fields, you cannot set to field order.
- you cannot add a diractory_listing to another node/entity type.

So, why not convert it into a proper Field API field?
This way, you can all settings in widget/formatter options.

Comments

clivesj’s picture

clivesj commented

I did propose this to Yoran. Actually I would like to move-up to version 7.x-3.x where we will incorporate not only the Field API but also File API (new streamwrappers). But Yoran has valid arguments to discuss this further first.
If you create the fields in Field API maintaining the module will be harder in case you want to modify the fields.
But maybe it is worthed, maybe not.
Let''s hear if there are more arguments for or against.

My main objective is to get 7.x stable as soon as possible.

ssaccone’s picture

ssaccone commented
Issue summary: View changes

This would be very useful for my site as well. To create custom layouts I've been forced to modify the Directory Listing content type. Ideally one would preserve this prototype and instead create new content types with a directory listing field.

clivesj’s picture

clivesj commented
Status: Active » Closed (outdated)