Document library columns
Document Library Pro gives you full control over the data displayed in the document library. You can do this using the
columns option in the Document Library Pro shortcode.
You can choose as many columns as you want and in any order. You must separate each column with a comma. It doesn’t matter if there are spaces before or after the comma, but there must not be any spaces before or after the = sign.
Here’s an example of a shortcode to display blog documents with columns for title, date, document author, excerpt and button:
idcolumn will display the document ID, which is a unique number used internally by WordPress for each document.
titlecolumn is the main document title.
contentcolumn will show the document content but will be truncated to 15 words. You can modify this length by setting the
excerptcolumn will show the document excerpt. It will be truncated to 55 words (the WordPress default) but themes and plugins sometimes override this value. To have precise control over the length, you can set the
imagecolumn will display the featured image (i.e. the document thumbnail) for the document or page (see
image_sizeoption to set a custom size).
datecolumn will display the date that the document was published.
date_modifiedcolumn will display the date that the document was last updated.
authorcolumn displays the document author’s display name.
tagscolumns apply to blog documents only (i.e.
document_type="document") and will display the categories or tags for each document (comma-separated if there is more than one).
statuscolumn will show the status of the document (e.g. draft, pending, publish, etc).
linkcolumn will link to the single document page. If you're using Document Library Pro with the Page Links To plugin, which lets you replace the single document page with another URL, then this will work with the button column. For example, this is useful if you're creating a document library and want to add 'Download' buttons to the document library. You can change the button text using the button text option.
Please note that column names are case sensitive and should always be lower case. (If you're using custom column headings then these can be any case.)
Custom field columns
Custom fields are a good way to include other types of content in the document library. You can use them to store links, buttons, icons, shortcodes from other plugins, etc. You should add the full HTML code or shortcode to the custom field so that the document library can display it correctly. If you’re adding shortcodes to your custom fields, you will need to set shortcodes to true.
You can add custom fields to your document library using the format
cf:<field name>. If you are using Advanced Custom Fields, the field name can be found under the “Field Name” column in the Custom Fields menu.
Here’s an example adding two custom fields –
Tip: You can use any custom fields plugin to create custom fields. We recommend Advanced Custom Fields for creating custom fields only; or Custom Posts Type UI or Pods if you need to create custom fields along with a custom document type and/or custom taxonomies.
Custom fields created using the Toolset plugin
If you're using Toolset to create your custom fields, then you need slightly different syntax to display them in the document library.
wpcf- to the start of the custom field name, so if you create a custom field called 'link' (for example) then the correct syntax will be
wpcf-link. This means that if you want to create a document library with columns for name and a custom field called 'link' then you would need to add it as follows:
ACF repeater fields
If you're using Advanced Custom Fields Pro repeater fields, you can create a column using the name of the parent repeater field. This column will list the content of all the repeater fields for that document, separated by commas. It is not possible to display repeater sub-fields as separate columns in the document library.
Custom taxonomy columns
For taxonomies (other than document categories and tags), use the format
tax:<taxonomy slug>. So, for example, to display for a custom taxonomy with the slug
document_type, you would use:
You can find the taxonomy slug by going to the WordPress admin and finding the main page which lists those taxonomies. For example, WooCommerce product categories are edited under the Products → Categories menu. On that page, the URL at the top of the screen shows “…edit-tags.php?taxonomy=product_cat….”. The ‘product_cat’ bit after the equals is the taxonomy slug you need to use.
author column displays the name of the WordPress user who created the document. If you're creating an author column and need more flexibility - for example because you are creating a document library and want to add the Document author - then you should use a different type of column instead. For example:
- You could use the categories or tags column and rename it to 'Author'.
- You could create a custom taxonomy for 'Author'.
Creating custom columns programmatically
Developer can use custom columns to display data programmatically which is not available as one of the standard document library columns.
Choosing your own column headings
You can set custom column headings by adding a : (colon) after the column name. You can rename as many columns as you like. You can use this method to change the wording and/or capitalization of column names.
If you don’t change the column heading then the default one will be used. For example, the default heading for the document title is "Title", but if you wanted the heading “"MY HEADING" instead, you would use:
[doc_library columns="title:MY HEADING,date,author,content"]
Here’s a more complex example where we want to set the title column heading to “Property Description”, the date column to “Added On”, a custom taxonomy to “Type” and a custom field to “Sale Price (£)”:
[doc_library document_type=property columns="title:Property Description,date:Added On,tax:listing_cat:Type,cf:valuation:Sale Price (£)"]
Note: In the above example, the taxonomy and custom field columns now have two colons – one to define the taxonomy (or custom field) name, and the other to set the column heading. This is perfectly fine as long as you use the correct syntax. For these column types, everything after the second colon will be used as the custom heading, including the space between the 2 words.
Removing a column heading
If you would like to remove the column heading completely use the keyword
blank after the colon. For example:
When you do this, the column names will be removed and only the sort arrows will be hidden. If you want to hide the header row completely then you can do this using custom CSS.
How to hide a column
You can easily hide columns simply by removing them from the list of columns in the document library. This will remove the column from the document library.
If you wish to hide a column on specific devices only (e.g. mobiles or document libraryts), please see the column_breakpoints option which allows you to do this.