CODEWITHSUNDEEP
plonedexterityplone-4.x
feesh
feesh

Reputation: 1248

Display a collection of custom Dexterity content types with specific headers

Dexterity questions all day, today!

So the next thing we're trying to do with these custom Dexterity "files" is to have collections of them throughout the website display in a table with certain headers. Is this possible? Currently the tabular_view that comes default with collections only shows these options:

Table columns default options

So it ends up looking like:

A collection of Dexterity "Files"

However, we want the table headers to be: Title, Type, Program, and Year, based on the fields in the Dexterity content type settings:

The main "tag" fields

Is this even possible? The reason we're using collections is because we want to show a subsection of these files within different areas of the website. Possibly also, we want to use collection portlets to display like, the three most recent files, on other pages.

Would we be better off using multiple instances of eea.facetednav everywhere?

Upvotes: 2

Views: 337

Answers (1)

hvelarde
hvelarde

Reputation: 2876

Take a look at the code of collective.nitf as we do what @keul is recommending at package installation.

specifically, you will need something like this for every field you want to add:

  <?xml version="1.0"?>
  <registry xmlns:i18n="http://xml.zope.org/namespaces/i18n"
    i18n:domain="plone">

    <records condition="installed plone.app.collection"
        interface="plone.app.querystring.interfaces.IQueryField"
        prefix="plone.app.querystring.field.genre">
      <value key="title" i18n:translate="">Genre</value>
      <value key="description" i18n:translate="">An NITF genre field</value>
      <value key="enabled">True</value>
      <value key="sortable">True</value>
      <value key="operations">
        <element>plone.app.querystring.operation.selection.is</element>
      </value>
      <value key="vocabulary">collective.nitf.AvailableGenres</value>
      <value key="group" i18n:translate="">NITF</value>
    </records>
  </registry>

Upvotes: 3

Related Questions