Hi Sam,
It is actually quite easy to achieve what you want and I guess your confusion comes from the fact that you are only looking at the
libraryInfo section of the web.config.
As you may know, the Libraries module is based on Generic Content, so it inherits a lot of functionality directly. We've tried to take out common features and behavior in the Generic Content module so that any other derived modules can benefit from that functionality. Metafields are an example. This is why when you add additional metafields in the web.config, you should do it in
<cmsEngine>/<metaFields> section. Then in
<libraryInfo>, you only specify which metafields are used by which library type. You may notice that the Description metafield is already present and this is why Rebecca didn't include instructions on how to add it. Here:
| <cmsEngine defaultProvider="Generic_Content"> |
| ... |
| <metaFields> |
| <add key="Libraries.Name" valueType="ShortText" visible="True" searchable="True" sortable="True" defaultValue="" /> |
| <add key="Libraries.Width" valueType="Integer" visible="True" searchable="True" sortable="True" defaultValue="" /> |
| ... |
| <add key="Libraries.Description" valueType="ShortText" visible="True" searchable="True" sortable="True" defaultValue="" /> |
| ... |
| </metaFields> |
| </cmsEngine> |
Possible values for the
valueType attribute are: ShortText, LongText, DateTime, Integer, FloatingPoint, Boolean, Guid, Binary. I hope things are a little clearer now. If not, we'll be happy to help further.
Regards,
Slavo
the Telerik team