File Info Table Reference

File Info Table Reference

Purpose

The File Info object is a foundation component of how and when Melody generates published content. It serves the purpose of providing the internal publishing API with information that helps it know what content to pull from other tables, what template to use and where the published content should go (as well as be URL-accessible).

Associated Perl classes

• MT::FileInfo

Fields

• fileinfo_id - integer not null auto_increment. - The primary key of the File Info table.
• fileinfo_blog_id - integer not null. - The blog associated with the File Info object.
• fileinfo_entry_id - integer. - The associated entry.
• fileinfo_url - string(255). - The URL of the published File Info object.
• fileinfo_file_path - text. - The file path of the published File Info object.
• fileinfo_templatemap_id - integer. - The template map ID of the associated template map.
• fileinfo_template_id - integer. - The ID of the template associated with the File Info object.
• fileinfo_archive_type - string(255). - The type of the published File Info object. Values are:
  • Author
  • Category
  • index
  • Individual
  • Monthly
  • Page
  • Yearly
• fileinfo_category_id - integer. - The category associatied with this File Info object.
• fileinfo_author_id - integer. - The user who created this File Info object.
• fileinfo_startdate - string(80). - A timestamp for date-based archives.
• fileinfo_virtual - boolean. - A flag which says whether or not this file actually exists. It is set to true during dynamic publishing.

Indexes

• mt_fileinfo_blog_id
• mt_fileinfo_entry_id
• mt_fileinfo_template_id
• mt_fileinfo_templatemap_id
• mt_fileinfo_archive_type
• mt_fileinfo_url
• mt_fileinfo_startdate
• mt_fileinfo_category_id
• mt_fileinfo_author_id

Developer Advice

It is strongly recommended that developers not alter entries in this table or add their own without being well-versed in how Melody creates them as it may disrupt the normal flow of publishing if plugins write to this table. Theme designers have no valid reason to modify or even access this table from their themes as it is meant to support Melody's internal publishing operations only.

Generally, this table should be treated as part of an internal API by third party developers.